Skip to content

add note to enable stable #540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jennyhickson merged 1 commit into from
Jan 5, 2026
Merged

add note to enable stable #540

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion source/Reviewers/curaterelease.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,8 @@ developed the release branch and the other will review it (**developer** and
.. image:: images/gh_screenshots/main_stable_dark.png
:class: only-dark border

* An admin will need to enable updates to the ``stable`` branch by adding it as
an exception to the target branches in the ``prevent updates`` ruleset.
* The **reviewer** will then review and commit the PR. When committing the
branch, ensure that the merge method is ``merge``. This should be the default
for the ``stable`` branch as we want to keep the history of ``main`` in the
Expand All @@ -82,7 +84,8 @@ developed the release branch and the other will review it (**developer** and
* Set ``merge`` as an allowed merge strategy and disable ``squash``.

* The **reviewer** can now ``merge`` the second PR.
* The admin **must** now revert the 2 settings above.
* The admin **must** now revert the 2 settings above in ``main`` and remove the
exception for ``stable`` in the ``prevent updates`` ruleset from earlier.


Tags and Releases
Expand Down