Repository navigation
Closed
Closed
CI: 'Linting' and 'Validation' jobs cannot pass on any PR — PARTIALLY FIXED, ROOT CAUSE REMAINS#1961
#2194 (+3)
Copy link
Labels
migrate:priority:normalDefault priorityDefault prioritymigrate:status:needs-more-infoMissing details to proceedMissing details to proceedmigrate:type:bugBug or defectBug or defectpriority:normalstatus:needs-more-infostatus:needs-template-fixtype:bug
Description
Status: REOPENED — Partially Fixed But Root Issues Remain
CRITICAL: This issue was prematurely closed as "completed" on 2026-08-20, but ~3,099 markdown linting errors remain unresolved in critical directories.
Problems
1. ❌ Linting — ~3,099 markdownlint errors remain (MD022/MD032/MD031)
Current Status:
- Total errors in repo: 3,099 errors
- Errors in target directories (
.github/agents/,agents/,docs/): 2,557 errors - PR fix: Restore frontmatter validator CLI flag parsing #2193 attempted fix by excluding
.github/reports/**and.github/projects/**from linting - But this only masked the problem in those directories — the main backlog remains
Error breakdown (target directories):
.github/agents/release.agent.md: Multiple MD031/MD032 violationsagents/ai-readiness-estimator-agent/README.md: 20+ MD022 violations (headings not surrounded by blank lines)docs/files: Widespread MD022/MD032 violations
Root Causes:
- MD022: Headings not surrounded by blank lines
- MD031: Code fences not surrounded by blank lines
- MD032: Lists not surrounded by blank lines
What PR #2193 Did NOT Fix:
- PR fix: Restore frontmatter validator CLI flag parsing #2193 added
.markdownlintignoreexclusions for.github/reports/**and.github/projects/** - This stopped the linting job from FAILING on those directories
- But the ~3,099 errors in
.github/agents/,agents/, anddocs/still exist - The CI linting job still fails when checking changed files in these directories
2. ⚠️ Validation — validate:footers still not properly scoped
Current Status:
- PR fix: resolve CI linting blocker in #1961 #2171 created a basic
validate:footersimplementation - But it doesn't properly handle the
--changed-only --base --headflags from the workflow - The validator is not respecting the changed-files-only scope that CI requires
Impact
❌ CI checks still fail on any PR that:
- Modifies
.github/agents/files (2,557+ errors) - Modifies
agents/files (significant portion of the 2,557) - Modifies
docs/files (significant portion of the 2,557)
❌ Related PRs blocked:
- Any PR touching agent documentation
- Any PR adding/updating documentation
- Branch name validation and other checks still cascading failures
Evidence
Output from npm run lint:md (current develop):
Summary: 3099 error(s)
Sample errors in target directories:
.github/agents/release.agent.md:161 error MD032/blanks-around-lists
agents/ai-readiness-estimator-agent/README.md:11 error MD022/blanks-around-headings
docs/[multiple files] error MD022/blanks-around-headings
Definition of Done
✅ Must complete ALL of the following:
- Fix all 2,557 markdown linting errors in
.github/agents/,agents/,docs/ - Verify
npm run lint:mdreturns 0 errors in those directories - Fix
validate:footersto properly handle--changed-onlyflag - Run full CI check on a test PR to confirm all validators pass
- Create a follow-up PR with fixes that passes all CI checks without overrides
Notes for Implementer
- Do NOT close this issue again until all errors are actually fixed
- Do NOT use
.markdownlintignoreto hide the problem — fix the actual markdown - All 2,557 errors need to be addressed for CI to be truly fixed
- This is the root cause why PR docs: Phase 5A Week 3 — Testing & Documentation Framework #1936 and others required admin merge overrides
Metadata
Metadata
Assignees
Labels
migrate:priority:normalDefault priorityDefault prioritymigrate:status:needs-more-infoMissing details to proceedMissing details to proceedmigrate:type:bugBug or defectBug or defectpriority:normalstatus:needs-more-infostatus:needs-template-fixtype:bug
Type
Fields
Priority
None yet
Activity
linear-code commentedon Aug 17, 2026
LS-2626
github-actions commentedon Aug 17, 2026
Issues preventing closure:
status:needs-more-info— resolve outstanding feedback firstWhat you can do:
meta:force-closelabel to this issue if closure is necessary despite incomplete requirementsAfter fixing: The issue will no longer show this warning and can be closed normally.
Need help? See the issue template guide: https://github.com/lightspeedwp/.github/issues/new/choose
github-actions commentedon Aug 17, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
Merge pull request #2171 from lightspeedwp/chore/session-662kx8
github-actions commentedon Aug 20, 2026
Milestone Allocation
ashleyshaw commentedon Aug 20, 2026
Reopened for Proper Resolution
This issue was closed prematurely after PR #2171 only addressed the missing
validate:footersscript. However, the core problem remains unresolved:Still Outstanding
Lintingjob failure — ~3,500 markdownlint errors (MD022/MD032 violations) across agent documentation files remain unfixed:agents/zendesk-support-agent/shared/core-prompt.mdhave massive backlog of violationslint:mdstep on every PRnpm run lint:allcannot pass until this is resolvedWhat Was Fixed
validate:footersscriptWhat Still Needs Fixing
Action Required
Implement one of the original options:
markdownlint-cli2 --fixrepo-wide as a single formatting commit.markdownlint-cli2.jsonclint:mdto changed files onlyReopened: 2026-08-20 — Incomplete resolution detected
Generated by Claude Code
1 remaining item
github-actions commentedon Aug 20, 2026
Milestone Allocation
fix: Resolve markdown linting errors (MD022, MD032, MD031, MD009)
fix: Exclude .github/reports and .github/projects from markdown linting
[-]CI: 'Linting' and 'Validation' jobs cannot pass on any PR[/-][+]CI: 'Linting' and 'Validation' jobs cannot pass on any PR — PARTIALLY FIXED, ROOT CAUSE REMAINS[/+]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:priority:normalmigrate:status:needs-more-infomigrate:type:bugstatus:needs-template-fixValid 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.