pr: only create backport branch once

[edvbld]

Hi all,

please review this patch that ensures that the /backport commit command will only create the backport commit (and corresponding branch) once. There is no need to try to do this multiple times, the cherry picking will result in the same result every time. If a user for some reasons issues the /backport command twice on a commit then this will now work.

Thanks,
Erik

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed

Reviewers

• Robin Westberg (@rwestberg - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/skara pull/1107/head:pull/1107
$ git checkout pull/1107

Update a local copy of the PR:
$ git checkout pull/1107
$ git pull https://git.openjdk.java.net/skara pull/1107/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1107

View PR using the GUI difftool:
$ git pr show -t 1107

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/skara/pull/1107.diff

[bridgekeeper]

👋 Welcome back ehelin! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (165c57ec)

[rwestberg]

Looks good!

[openjdk]

@edvbld This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

🔍 One or more changes in this pull request modifies files in areas of the source code that often require two reviewers. Please consider if this is the case for this pull request, and if so, await a second reviewer to approve this pull request before you integrate it.

🌎 Applicable reviewers for one or more changes in this pull request are spread across multiple different time zones. Please consider waiting with integrating this pull request until it has been out for review for at least 24 hours to give all reviewers a chance to review the pull request.

After integration, the commit message for the final commit will be:

pr: only create backport branch once

Reviewed-by: rwestberg

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 4 new commits pushed to the master branch:

• b404a14: forge: GitLab members endpoint return 404 for non-members
• 87c55b2: 568: RFR mails from the list are not copied to github
• 3d6d56f: 943: remote: GitLab: You can only delete protected branches using the web interface
• 74c9069: build: update to Gradle 6.8.3

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[edvbld]

/integrate

[openjdk]

@edvbld Since your change was applied there have been 9 commits pushed to the master branch:

• 1137b55: 905: Github UI code markdown can fail to get copied correctly into email
• d9b551d: 769: Replies to e-mail comments on GitHub are threaded incorrectly
• 35dd1da: Backport security level should be inherited from main issue
• f12ee73: 958: Add test cases for known corner cases for synclabel bot
• 4ca65de: 715: Generated email wrongly includes previous unrelated comments
• b404a14: forge: GitLab members endpoint return 404 for non-members
• 87c55b2: 568: RFR mails from the list are not copied to github
• 3d6d56f: 943: remote: GitLab: You can only delete protected branches using the web interface
• 74c9069: build: update to Gradle 6.8.3

Your commit was automatically rebased without conflicts.

Pushed as commit 2ff465b.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.