Conversation
protect-main required Lint, Test, Build (amd64) and Build (arm64) — the names the Go CI emitted — so ci.yml published them to unblock the merge. The ruleset now names the checks the reusables actually emit, and those four jobs come out again: Lint and Test were reflecting the rust job rather than doing anything, and the Build pair has no name left to satisfy. That loses the arm64 build check. Nothing else in CI compiles for that target, and release.yml publishes an arm64 binary, so it is a real gap — recorded here rather than left to be rediscovered. debian-tests.yml loses its path filter. It becomes a required check, and a required check that does not run on every pull request blocks the merge for ever on any PR that misses its paths. Pages goes: the workflow never had anywhere to deploy. It failed with "Failed to create deployment (status: 404)" because Pages was never enabled on the repository, and both candidate hosts return 404. The README pointed at one of them. site/ stays. It is not a copy of docs/ — 46 pages, of which at least twelve guides exist nowhere else. Nothing builds it now, so it will rot unless it is either published or removed deliberately. Signed-off-by: Jaro-c <75870284+Jaro-c@users.noreply.github.com>
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.
protect-main required
Lint,Test,Build (amd64)andBuild (arm64)— the names the Go CI emitted.ci.ymlpublished them from #70 so the cutover could merge; the ruleset now names the checks the reusables actually emit, and those four jobs come out again.LintandTestwere reflecting therustjob rather than doing anything themselves, so nothing is lost there.Build (amd64)andBuild (arm64)did do work, and that goes. Nothing else in CI compiles for arm64, andrelease.ymlpublishes an arm64 binary, so that is a real gap. It is recorded here rather than left to be rediscovered. The amd64 side is still covered bydebian / dpkg-buildpackage, which builds the package for the musl target.debian-tests.ymlloses its path filter. It becomes a required check, and a required check that does not run on every pull request blocks the merge for ever on any PR that misses its paths — the reason those bridges were inci.ymlto begin with.Pages
The workflow never had anywhere to deploy. It failed with
because Pages is disabled at the organisation level: Settings → Pages reads "Pages on this repository are disabled". Both candidate hosts return 404, and the README pointed at one of them. The workflow and that link go.
site/stays. It is not a copy ofdocs/— 46 content pages, of which at least twelve guides exist nowhere else. Nothing builds it now, so it will rot unless it is either published or removed deliberately; worth a decision either way.Test plan
yaml.safe_loadaccepts both changed workflows.debian / dpkg-buildpackageruns on this PR with no path filter.Signed-off-by: Jaro-c 75870284+Jaro-c@users.noreply.github.com