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
{{ message }}
Repository navigation
ci: stop Generate Index pushing [skip ci] commits to PR branches #219
Follow-up from #218 (Copilot review) and part of #211.
Problem
.github/workflows/generate-index.yml runs on pull requests that touch .apm/**, .github/prompts/** or .github/agents/**. When INDEX.md/README.md change, it commits docs: Update index [skip ci] and pushes to the PR branch with GITHUB_TOKEN. Commits pushed with GITHUB_TOKEN, and commits marked [skip ci], don't trigger workflows. So the PR's new head has no check runs.
This affects exactly the PRs the SkillSpector scan targets, including materialize review PRs that change .github/agents/**. Once Scan AI primitives (or any other check) is required in the ruleset, those PRs would wait forever.
Proposed solution
Pick one:
On pull_request, fail with a "run bash scripts/generate-index.sh and commit" message instead of pushing. Lefthook already regenerates and re-stages the index locally (.lefthook.toml, generate-index command with stage_fixed). Keep the push only for main.
Or push with a CI-triggering App token and drop [skip ci].
Do this before making Scan AI primitives a required check (see the SkillSpector section of CONTRIBUTING.md).
Activity
ci: check the index on PRs instead of pushing [skip ci] commits
ci: check the index on PRs instead of pushing [skip ci] commits