You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fail-on-error: false # Continue workflow on validation errors
35
38
```
36
39
37
40
### Post-Merge Link Checking
38
41
39
-
The `docs-link-check.yaml` workflow runs after merges to main and on a weekly schedule to check for broken links and create GitHub issues automatically:
42
+
The `docs-link-check.yaml` workflow runs after merges to main and on a weekly schedule to check for broken links and cross-references:
40
43
41
44
- Runs after merges to main that affect documentation
42
45
- Runs weekly on Monday mornings
43
-
- Creates GitHub issues with broken link details
44
-
- Sends Slack notifications when issues are found
46
+
- Uses lychee for robust link checking
47
+
- Detects broken internal cross-references
48
+
- Creates GitHub issues with detailed error information and fix guidance
45
49
46
50
## Features
47
51
@@ -81,40 +85,50 @@ The documentation workflow is designed for maximum efficiency using a phase-base
81
85
82
86
### Phase 4: Preview Generation
83
87
- Generate preview URLs for documentation changes
84
-
- Build links to new documentation
88
+
- Create direct links to specific changed documents
89
+
- Extract document titles from markdown headings
85
90
86
91
### Phase 5: Results Aggregation
87
92
- Collect results from all validation steps
88
93
- Normalize into a unified JSON structure
89
94
- Calculate success metrics and statistics
90
-
- Generate summary badge
95
+
- Generate status badge based on success percentage
91
96
92
97
### Phase 6: PR Comment Management
93
98
- Find existing comments or create new ones
94
99
- Format results in a user-friendly way
95
100
- Provide actionable guidance for fixing issues
101
+
- Include direct links to affected documents
96
102
97
103
## Unified Results Reporting
98
104
99
-
The workflow now aggregates all validation results into a single JSON structure:
105
+
The workflow aggregates all validation results into a single JSON structure:
100
106
101
107
```json
102
108
[
103
109
{
104
-
"name": "markdown-lint",
105
-
"status": "success|failure",
106
-
"output": "Raw output from the validation tool",
110
+
"name": "Markdown Linting",
111
+
"status": "success|failure|warning",
112
+
"details": "Details about the validation result",
107
113
"guidance": "Human-readable guidance on how to fix",
108
114
"fix_command": "Command to run to fix the issue"
109
115
},
110
116
// Additional validation results...
111
117
]
112
118
```
113
119
120
+
### Status Badge Generation
121
+
122
+
Results are automatically converted to a GitHub-compatible badge:
123
+
124
+
- ✅ **Passing**: 100% of validations pass
125
+
- ⚠️ **Mostly Passing**: ≥80% of validations pass
126
+
- ❌ **Failing**: <80% of validations pass
127
+
114
128
### Benefits of Unified Reporting:
115
129
116
130
1. **Consistency**: All validation tools report through the same structure
117
-
2. **Integration**: JSON output can be easily consumed by other tools or dashboards
131
+
2. **Visibility**: Status badge clearly shows overall health at a glance
118
132
3. **Statistics**: Automatic calculation of pass/fail rates and success percentages
119
133
4. **Diagnostics**: All validation results in one place for easier debugging
120
134
5. **Extensibility**: New validators can be added with the same reporting format
0 commit comments