Repository navigation
Closed
Closed
Copy link
Labels
area:buildsmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:priority:criticalProduction/launch-blockingProduction/launch-blockingmigrate:status:needs-more-infoMissing details to proceedMissing details to proceedmigrate:type:bugBug or defectBug or defectpriority:criticalstatus:needs-more-infostatus:needs-triagetype:bug
Milestone
Description
Status: REOPENED — Partially Fixed But Validators Still Blocking PRs
CRITICAL: This issue was prematurely closed as "completed" on 2026-08-20, but validators are still blocking legitimate PRs. This is the root cause of PR #1936 requiring admin override.
Current Status (2026-08-20 Post-Merge)
✅ Partially Fixed:
- PR fix: Restore frontmatter validator CLI flag parsing #2193 fixed frontmatter validator CLI flag parsing (minimist-based)
- PR fix: resolve CI linting blocker in #1961 #2171 added validate:footers implementation
- lint-md-changed.cjs now filters by
.markdownlintignorepatterns
❌ Still Broken:
- 3,099 markdown linting errors remain in repository
- 2,557 errors in target directories (
.github/agents/,agents/,docs/) - Validators still fail on legitimate PRs with documentation changes
- Branch name validation still blocking some valid branch names
- Linting & Links validator still cascading failures
Test Case: PR #1936 Status
PR #1936 "Phase 5A Week 3 — Agentic Release Workflow" required admin merge override despite being 100% valid:
| Check | Status | Root Cause |
|---|---|---|
| Testing | ✅ PASS | 9/9 tests |
| CodeRabbit | ✅ PASS | Code review passed |
| Project-Issue Linking | ✅ PASS | 53 projects validated |
| Branch Name Validation | ❌ FAIL | Validator logic issue |
| Frontmatter Validation | Fixed by PR #2193 but not verified on PR #1936 | |
| Linting & Links | ❌ FAIL | 2,557+ errors in agent/docs markdown |
| Secrets Scan | ❌ FAIL | False positive (no secrets present) |
Result: Merged via admin override because validators were incorrectly rejecting valid content
Root Causes
1. Linting Backlog Blocks New Changes
- Issue: 3,099 existing markdown linting errors in repository
- Impact: Any PR modifying
.github/agents/,agents/, ordocs/files fails linting - Root Cause: PR fix: Restore frontmatter validator CLI flag parsing #2193 only masked the issue in
.github/reports/**and.github/projects/**by excluding them from linting — did not fix the actual errors
2. Branch Name Validation Logic
- Issue: Valid branch names still being rejected
- Status: Validator script may have incorrect regex or pattern matching
- Impact: Blocks legitimate PRs with valid branch naming
3. Secrets Scan False Positives
- Issue: Scan failing without legitimate secrets present
- Status: Validator configuration or scan logic issue
- Impact: Blocks all PRs regardless of content
4. Frontmatter Validation Still Has Issues
- Status: PR fix: Restore frontmatter validator CLI flag parsing #2193 fixed CLI flag parsing but validator still fails on some files
- Impact: Documentation PRs blocked even after PR fix: Restore frontmatter validator CLI flag parsing #2193
Immediate Actions Required
Phase 1: Fix Markdown Linting (Must Complete First)
- Fix all 2,557 markdown linting errors in
.github/agents/,agents/,docs/ - Verify
npm run lint:mdreturns 0 errors - Verify
npm run lint:allpasses completely
Phase 2: Verify Validator Fixes
- Test frontmatter validator on documentation files
- Fix branch name validation logic if still failing
- Debug secrets scan false positives
- Verify Branch Name validation works
Phase 3: Integration Testing
- Create test PR modifying
.github/agents/,agents/,docs/ - Verify ALL CI checks pass without admin override
- Verify Mergify can auto-merge
Definition of Done
✅ Must complete ALL of the following:
- All 2,557 markdown linting errors fixed in target directories
-
npm run lint:allpasses with 0 errors - Frontmatter validator passing on all documentation
- Branch name validation not rejecting valid names
- Secrets scan not producing false positives
- New PR created and merged WITHOUT admin override
- Mergify auto-merge working for legitimate PRs
- PR docs: Phase 5A Week 3 — Testing & Documentation Framework #1936 (or similar test case) can be tested and confirmed working
Related Issues & PRs
- Related to CI: 'Linting' and 'Validation' jobs cannot pass on any PR — PARTIALLY FIXED, ROOT CAUSE REMAINS #1961 — Markdown linting backlog is primary blocker
- Test Case: PR docs: Phase 5A Week 3 — Testing & Documentation Framework #1936 (merged via admin override, needs re-validation)
- Attempted Fixes:
- PR fix: Add missing validate:frontmatter:changed npm script for CI validation #1999: Added validate:frontmatter:changed script
- PR fix: Resolve CI validator failures (#1961, #1966) #2190: Attempted validator fixes (partially effective)
- PR fix: Restore frontmatter validator CLI flag parsing #2193: Frontmatter CLI flag parsing + linting exclusions (incomplete)
- PR fix: resolve CI linting blocker in #1961 #2171: Added validate:footers implementation
Notes for Implementer
- DO NOT CLOSE this issue until all validators are confirmed working on legitimate PRs
- The core issue is that legitimate PRs are being rejected by CI validators
- PR docs: Phase 5A Week 3 — Testing & Documentation Framework #1936 is the primary evidence that validators are still broken
- All fixes must be verified with integration testing on a real PR before closure
Metadata
Metadata
Assignees
Labels
area:buildsmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:priority:criticalProduction/launch-blockingProduction/launch-blockingmigrate:status:needs-more-infoMissing details to proceedMissing details to proceedmigrate:type:bugBug or defectBug or defectpriority:criticalstatus:needs-more-infostatus:needs-triagetype:bug
Type
Fields
Priority
None yet
Activity
linear-code commentedon Aug 17, 2026
LS-2629
github-actions commentedon Aug 17, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
github-actions commentedon Aug 17, 2026
Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)
The issue will remain open and flagged until the body is corrected.
Please update the issue with one of the official templates:
If this was opened by automation, update the automation to preserve the template sections before creating the issue.
fix: Add missing validate:frontmatter:changed npm script for CI valid…
github-actions commentedon Aug 18, 2026
Milestone Allocation
10 remaining items
[-]CI Validators Rejecting Valid Content — Branch Name, Frontmatter, Linting Failures[/-][+]CI Validators Rejecting Valid Content — PARTIALLY FIXED, STILL BLOCKING PRs[/+]fix: resolve all markdown linting errors across repository
github-actions commentedon Aug 21, 2026
Milestone Allocation
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:area:cimigrate:priority:criticalmigrate:status:needs-more-infomigrate:type:bugValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.