ci: retire skill-drift.yml (no-op stub) - #856
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Deletes
.github/workflows/skill-drift.yml.Why
This workflow calls
projectbluefin/actions/.github/workflows/skill-drift-check.yml, which is a deprecated no-op stub. Its own header says so:Its only step echoes
"Skill drift check removed. Delete skill-drift.yml from consumer repo."and exits 0 without inspecting any changed path.So this workflow has been running on every PR and returning a silent green result regardless of what changed. A green check that proves nothing is worse than no check, because it reads as evidence that a skill update was not needed.
Five repos carried this: bluefin, bluefin-lts, dakota, knuckle, testsuite.
commonnever wired it up.Safety
skill-driftis not a required status check in this repo (verified against the ruleset), so removing it cannot stall a PR or the merge queue.Policy
Per
projectbluefin/commondocs/factory/agentic-model.md, process conventions are enforced at developer time bypre-commit; CI may re-run that suite as a single aggregate step, and bespoke per-convention CI jobs are banned.The obligation to update skills alongside implementation is unchanged — only the false claim that CI enforced it is gone.
Retirement record: https://github.com/projectbluefin/common/blob/main/docs/skills/skill-drift.md