And provide better instructions about how to merge manually.
One thing that people don't realize is that the second PR number (in backport pull request) is autogenerated by GitHub, and had to be removed manually by hand before we click "Squash and Merge" button.
If we don't want to have to remember to remove that manually, then utilize the automerge feature.
As a reminder, automerge will be triggered if:
In case of miss-islington's own PR, if the PR was approved by a core dev (has awaiting merge label), tests all passing, CLA signed, and no do-not-merge label.
In case it is not miss-islington's own PR: same as the above, with addition of automerge label
The text was updated successfully, but these errors were encountered:
I wonder if the right place for this content is https://devguide.python.org/committing/ or if there is a need for a dedicated page which helps core devs understand the features of the bots?
There already is #520 to make the above page simpler, but I feel more text on that page will just be invisible. But perhaps when it is re-written to be a more of a step-by-step guide, it can delegate to specific sections of this new page dedicated to bots when pointing out the workflow.
And provide better instructions about how to merge manually.
One thing that people don't realize is that the second PR number (in backport pull request) is autogenerated by GitHub, and had to be removed manually by hand before we click "Squash and Merge" button.
If we don't want to have to remember to remove that manually, then utilize the automerge feature.
As a reminder, automerge will be triggered if:
awaiting mergelabel), tests all passing, CLA signed, and nodo-not-mergelabel.automergelabelThe text was updated successfully, but these errors were encountered: