From ccb2da2231a46f52d333feabc51c82f89f6b4a29 Mon Sep 17 00:00:00 2001 From: Suzzy Nyakotey Date: Tue, 13 Oct 2026 13:13:29 +0000 Subject: [PATCH] Move update branch section after submitting --- getting-started/pull-request-lifecycle.rst | 32 +++++++++++----------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst index 5cba5f233..e51ab3a93 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -526,6 +526,22 @@ another so they can easily verify whether their comments have been addressed. The commits will be squashed when the pull request is merged. +:guilabel:`Update branch` button +================================ + +You can click on the :guilabel:`Update branch` button to merge the latest +changes from the base branch (usually ``main``) into the PR. +This is useful to :ref:`keep the CI green ` for old PRs, +or to check if a CI failure has been fixed in the base branch. + +If the PR is very old, it may be useful to update the branch before merging to +ensure that the PR does not fail any CI checks that were added or changed since +CI last ran. + +Do not click :guilabel:`Update branch` without a good reason because it notifies +everyone watching the PR that there are new changes, when there are not, +and it uses up limited CI resources. + Converting an existing patch from b.p.o to GitHub ================================================= @@ -685,22 +701,6 @@ If you identify such flaky behavior, look for an issue in the `issue tracker`_ that describes this particular flakiness. Create a new issue if you can't find one. -:guilabel:`Update branch` button -================================ - -You can click on the :guilabel:`Update branch` button to merge the latest -changes from the base branch (usually ``main``) into the PR. -This is useful to :ref:`keep the CI green ` for old PRs, -or to check if a CI failure has been fixed in the base branch. - -If the PR is very old, it may be useful to update the branch before merging to -ensure that the PR does not fail any CI checks that were added or changed since -CI last ran. - -Do not click :guilabel:`Update branch` without a good reason because it notifies -everyone watching the PR that there are new changes, when there are not, -and it uses up limited CI resources. - Committing/rejecting ====================