Copilot commented on code in PR #55484:
URL: https://github.com/apache/arrow/pull/55484#discussion_r4532017636
##########
docs/source/developers/release.rst:
##########
@@ -621,12 +621,26 @@ Be sure to go through on the following checklist:
.. code-block:: Bash
- # You can run the script with BUMP_TAG=0 and BUMP_PUSH=0
- # this will avoid default pushing to main and pushing the tag
- # but you will require to push manually after reviewing the commits.
# dev/release/post-10-bump-versions.sh 10.0.0 11.0.0
dev/release/post-10-bump-versions.sh X.Y.Z NEXT_X.NEXT_Y.NEXT_Z
+ This script pushes a ``bump-versions-NEXT_X.NEXT_Y.NEXT_Z`` branch to
+ your fork. We can't push to ``main`` directly because ``main`` requires
+ the "Merge check" status check. You need to create a pull request from
+ the branch with the title that the script shows
+ (``MINOR: [Release] Update versions for NEXT_X.NEXT_Y.NEXT_Z-SNAPSHOT``)
+ and merge it. You can run the script with ``BUMP_PUSH=0`` to review the
+ commits before you push them.
Review Comment:
For a major release, `BUMP_PUSH=0` still leaves `BUMP_TAG=1`, so this
documented review command looks for an already-merged bump PR after creating
the local commits and fails on a normal first run. Disable tagging as well for
the pre-merge review run, and reserve `BUMP_DEFAULT=0 BUMP_TAG=1` for tagging
after the PR is merged.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
