Repository navigation
ci: run on the 0.x release branch and version branches after it - #86
Conversation
The trunk is renamed from main to 0.x, one release branch per major, as in druxt.js. CI and CodeQL run on pushes to any '*.x' branch, and on every pull request whatever its base. CodeQL listed develop, a branch this repository never had, so it ran on its schedule only. Renovate targets every version branch, changesets reads 0.x as its base, and the README badges follow 0.x. CONTRIBUTING says which branch to work from.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Document the release branch convention CONTRIBUTING.md, .changeset/config.json |
Contributor guidance describes major and older-minor release branches. Changesets now uses 0.x as its base branch. |
Apply release branches to automation .github/workflows/ci.yml, .github/workflows/codeql-analysis.yml, renovate.json, README.md |
CI and CodeQL push triggers match *.x branches, and their pull request triggers accept any target branch. Renovate targets versioned .x branches, and README badges reference 0.x. |
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Other
Possibly related PRs
- druxt/module-template#82: Adds a release workflow triggered from
mainand*.xbranches, which uses the release branch naming and behaviour described here.
Merge Risk: 
Minimal · up to 59e58
-
The branch-targeting changes present no concrete merge-blocking risk.
Pre-merge checks: 
5
-
Full details: Title check
-
Explanation
The title says the change makes CI run on the 0.x release branch and on version branches after it. The raw summary and objectives show that ci.yml now runs on pushes to *.x branches and on pull requests regardless of base branch. The title covers the main CI change. It leaves out the wider branch migration, which touches CodeQL, Renovate, the Changesets baseBranch, the README badges, and CONTRIBUTING.md. That is expected for a short title, so the title is related to the main change.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
The trunk is now
0.x, one release branch per major, as in druxt.js.mainis renamed on GitHub and replaced on the mirror, and the open pull requests moved with it. This change updates the configuration that still namedmain.What changes
.github/workflows/ci.ymlmainonly'*.x', and every pull request whatever its base.github/workflows/codeql-analysis.ymldevelop, which never existed here, so only the weekly schedule ranrenovate.jsonmain<major>.xor<major>.<minor>.xbranch.changeset/config.jsonbaseBranch: mainbaseBranch: 0.xREADME.mdmain0.xCONTRIBUTING.md0.xand target itA repository made from the template starts on
0.x, since GitHub copies the default branch with its name.Testing
0.x,1.x,1.2.xand10.x, and notmainorfeature/x.0.x, so its own CI run checks the newpull_requesttrigger.#82 still names
mainin the release workflow. It moves to'*.x'when it is rebased onto this.Summary by CodeRabbit