Skip to content

CI Validators Rejecting Valid Content — PARTIALLY FIXED, STILL BLOCKING PRs #1966

Closed

Description

@ashleyshaw

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:

❌ 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 ⚠️ PARTIALLY 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/, or docs/ 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


Immediate Actions Required

Phase 1: Fix Markdown Linting (Must Complete First)

  1. Fix all 2,557 markdown linting errors in .github/agents/, agents/, docs/
  2. Verify npm run lint:md returns 0 errors
  3. Verify npm run lint:all passes completely

Phase 2: Verify Validator Fixes

  1. Test frontmatter validator on documentation files
  2. Fix branch name validation logic if still failing
  3. Debug secrets scan false positives
  4. Verify Branch Name validation works

Phase 3: Integration Testing

  1. Create test PR modifying .github/agents/, agents/, docs/
  2. Verify ALL CI checks pass without admin override
  3. 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:all passes 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


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

Activity

  1. linear-code commented on Aug 17, 2026

    @linear-code
  2. github-actions commented on Aug 17, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 3 day(s)
    • SLA state: Within SLA
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-20T18:58:40.737Z

    Maintained by project-meta-sync workflow.

  3. github-actions commented on Aug 17, 2026

    @github-actions
    Contributor

    ⚠️ This issue does not follow a required issue template.

    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.

  4. added a commit that references this issue on Aug 18, 2026
    078d65c
  5. added this to the v1.0 milestone on Aug 18, 2026
  6. github-actions commented on Aug 18, 2026

    @github-actions
    Contributor

    Milestone Allocation

    ✅ 2026-08-18T11:04:02.908Z [main] Starting allocation...
    ✅ 2026-08-18T11:04:03.175Z [main] Allocating issue #1966...
    [@octokit/request] "PATCH https://api.github.com/repos/lightspeedwp/.github/issues/1966" is deprecated. It is scheduled to be removed on Fri, 10 Mar 2028 00:00:00 GMT. See https://docs.github.com/en/rest/about-the-rest-api/api-versions
    ✅ 2026-08-18T11:04:04.281Z [allocate-issue] Allocated issue #1966 to milestone #76
    ✅ 2026-08-18T11:04:04.281Z [summary] Allocation complete. | Allocated: 0 PR(s), 1 issue(s) | Skipped: 0 | Errors: 0
    
  7. 10 remaining items

  8. changed the title [-]CI Validators Rejecting Valid Content — Branch Name, Frontmatter, Linting Failures[/-] [+]CI Validators Rejecting Valid Content — PARTIALLY FIXED, STILL BLOCKING PRs[/+] on Aug 20, 2026
  9. github-actions commented on Aug 21, 2026

    @github-actions
    Contributor

    Milestone Allocation

    
    
  10. self-assigned this
    on Sep 8, 2026
  11. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:area:ci
    • migrate:priority:critical
    • migrate:status:needs-more-info
    • migrate:type:bug

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions