Stefan/evcc-io
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: name backport branch after the bugfix release (#32375)

Browse source
This commit is contained in:
andig 2026-08-01 12:41:45 +02:00 • committed by GitHub
parent 6257876cfa
commit eb95f2166e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 19 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

8
CONTRIBUTING.md
View file

@ -91,10 +91,10 @@ and the demo instance untouched.
To move a merged pull request onto a release branch, comment `/backport` on it.
The pull request has to carry the `bug` label and must not be marked `(BC)`,
only non-breaking bugfixes are backported.
The commit is cherry-picked onto the branch of the current release line, e.g.
`release/0.313`, and a pull request is opened against it. The branch is created
at the newest tag of that line if it does not exist yet. Pass a branch name,
`/backport release/0.312`, to service an older line.
The commit is cherry-picked onto the branch of the next bugfix release, e.g.
`release/0.313.1`, and a pull request is opened against it. The branch is
created at the newest tag of that line if it does not exist yet. Pass a branch
name, `/backport release/0.312.2`, to service an older line.
## Debugging in VS Code