Repository navigation
chore: drop the consumer CI workflow - #35
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Every repository is now gated by the organization required workflow in
webinertia/.github, which runs the same jobs directly. This file is the olduses:path, and it still carries the@1.0.xref — the duplicated fact whose drift caused the original incident.Parity was verified side by side on a real PR before removal: on the same commit, the inlined
Mago,Test(all six legs) andCodecovjobs all reported the same conclusions as this file'sqa / ...checks.Removing it also removes the last surviving
@1.0.xreference in this repository.Behaviour that goes with it
This file also triggered on pushes to version branches and on version tag pushes. The required workflow covers pull requests into version branches, which is the path that matters — direct pushes are now blocked by the ruleset's require-pull-request rule, and a release tag points at a commit already validated on its branch.