chore(ci): align with bitbox_flutter — develop default, auto-tag, auto-release-pr#3
Merged
Merged
Conversation
…-tag, auto-release-pr) Bring the repo's CI plumbing in line with the DFXswiss/bitbox_flutter template now that develop is the default branch: * test.yml → test.yaml, renamed `name: test` to `name: PR checks`, trigger expanded to push develop+main. * auto-release-pr.yaml: every push to develop opens (or reuses) a `Release: develop -> main` PR. * auto-tag.yaml: every push to main bumps the patch version and creates a GitHub release. Adapted from the bitbox_flutter template to also emit the `go/vX.Y.Z` submodule tag — without it `go install` for the audit CLI cannot resolve the package (see CONTRIBUTING). Repo settings (default branch develop, branch rulesets mirroring bitbox_flutter) were applied directly via the GitHub API.
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.
Summary
Brings bitbox-testkit's CI/release plumbing in line with the DFXswiss/bitbox_flutter template, per the org-wide pattern (develop = default, develop→main release PRs, auto-tag on merge to main).
Changes in this PR (workflows)
test.yml→test.yaml,name: test→name: PR checks, trigger expanded topush: [develop, main](was[main]only)..github/workflows/auto-release-pr.yaml— literal port of bitbox_flutter's auto-release-pr. Every push to develop opens (or reuses) aRelease: develop -> mainPR..github/workflows/auto-tag.yaml— patch-bumps the latestvX.Y.Ztag on every push to main and cuts a GitHub release.vX.Y.Z, the workflow also createsgo/vX.Y.Zon the same commit. Required by Go's submodule resolver because the module lives at/go/— without the prefixed tag,go install github.com/DFXswiss/bitbox-testkit/go/cmd/bitbox-audit@vX.Y.Zfails. CONTRIBUTING.md already documented this two-tag requirement; the workflow now enforces it instead of relying on the human releaser.Changes already applied out-of-band (GitHub API)
main→develop.develop(id 16488485): deletion blocked, non-fast-forward blocked, PR required (0 approvals, squash-only). Mirrors bitbox_flutter.main(id 16488487): deletion blocked, non-fast-forward blocked, PR required (1 approval, merge-commit only). Mirrors bitbox_flutter.Validation
yaml.safe_loadok).test.yamlkeeps the existing 6-job matrix unchanged (onlyname, triggers, and filename touched).What this does NOT change
analyze-and-testjob structure — bitbox-testkit's stack is Go + TS, so the job content must differ from bitbox_flutter; only the workflow scaffolding (triggers, naming, auto-* flows) is brought in line.