chore: adopt gt repo governance - #6
Closed
pedromvgomes wants to merge 2 commits into
Closed
Conversation
Adds the committed .gt-repo.yaml that declares this repository's governance, plus the files gt renders from it: Dependabot config for the three ecosystems detected here (github-actions, gomod, npm at /web), the PR gate caller, the weekly drift-repair caller, and Dependabot auto-merge. checks.required was seeded from the job names ci.yml already produces, so the gate waits on exactly the checks this repo already enforces. Branch protection needs a single required check, "PR / Gate", which aggregates the rest. That name never changes, so protection is configured once.
Re-rendered after gt's shared policy consolidated three different cooldowns and two prefix schemes into one: 7-day cooldown, build/ci prefixes with include: scope, and a 25 PR limit. The gate caller also gained the `edited` trigger, so a corrected PR title re-runs the check instead of staying red.
Contributor
Author
|
Closing: gt's pipeline design changed materially. gt will own the CI entry point ( Reopening against the new shape rather than migrating twice. Branch kept for reference. |
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.
First repository onto
gt repo. Generated bygt repo init+gt repo sync, not hand-written..gt-repo.yaml— the declaration; everything else is rendered from it.github/dependabot.yml— three ecosystems detected here (github-actions, gomod, npm at/web), with the shared 3-day cooldown and conventional commit prefixes.github/workflows/gate.yml— thin caller for the PR gate.github/workflows/gt-sync.yml— weekly drift repair, opens a PR only when something changed.github/workflows/dependabot-auto-merge.yml— daily batch merge for patch/minor bumpschecks.requiredwas seeded from the job namesci.ymlalready produces, so the gate waits on exactly what this repo already enforces.Expected to fail until gt is released
The callers pin
pedromvgomes/gt/.github/workflows/reusable-gate.yml@v0, and that tag does not exist yet — the gate will error with "workflow not found". Thegovernancejob would also fail, because it installs gt from the latest release andgt repoonly exists on an unreleased branch.Both clear once gt cuts the release. This PR is the test that the workflow layer actually works; do not merge it while the gate is red for those reasons.
Branch protection will need exactly one required check,
PR / Gate, replacing any per-job entries. That name never changes.