aboutsummaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorseth <getchoo@tuta.io>2023-07-16 17:28:14 -0400
committerseth <getchoo@tuta.io>2023-07-16 17:28:52 -0400
commited2f680202316c2ecf33a8926866a47da17f44e2 (patch)
tree8268acb0b536bedc479dba734305e3415a79695b /CONTRIBUTING.md
parent5e0df9b6965fae285d35580d19d1ab9bbc39c16a (diff)
downloadPrismLauncher-ed2f680202316c2ecf33a8926866a47da17f44e2.tar.gz
PrismLauncher-ed2f680202316c2ecf33a8926866a47da17f44e2.tar.bz2
PrismLauncher-ed2f680202316c2ecf33a8926866a47da17f44e2.zip
chore(docs): add backporting info to CONTRIBUTING.md
Signed-off-by: seth <getchoo@tuta.io>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4bca126f..b2795ce4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -61,3 +61,10 @@ As a bonus, you can also [cryptographically sign your commits][gh-signing-commit
[gh-signing-commits]: https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
[gh-vigilant-mode]: https://docs.github.com/en/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits
+
+
+## Backporting to Release Branches
+
+We use [automated backports](https://github.com/PrismLauncher/PrismLauncher/blob/develop/.github/workflows/backport.yml) to merge specific contributions from develop into `release` branches.
+
+This is done when pull requests are merged and have labels such as `backport release-7.x` - which should be added along with the milestone for the release.