572: Auto-correct PR title if it is a prefix of the JBS issue title

[magicus]

The PR bot should auto-correct PR titles if they are a known prefix of a JBS issue title instead of showing a warning that there is a mismatch between PR and JBS title.

---

Progress

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

Issue

• SKARA-572: Auto-correct PR title if it is a prefix of the JBS issue title

Reviewers

• Robin Westberg (@rwestberg - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/skara pull/1023/head:pull/1023
$ git checkout pull/1023

[bridgekeeper]

👋 Welcome back ihse! 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 (7bf4816)

[rwestberg]

Looks good!

[openjdk]

@magicus 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.

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

572: Auto-correct PR title if it is a prefix of the JBS issue title

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:

• 3acaa00: cli: rework git-backport
• c2e2ade: pr: add /clean command
• ab4c1f1: Initial version of census upgrade bot
• a8fe187: 574: git-info should use info from commit notifications

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@rwestberg) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[magicus]

/integrate

[openjdk]

@magicus
Your change (at version 7bf4816) is now ready to be sponsored by a Committer.

[edvbld]

/sponsor

[openjdk]

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

• 3acaa00: cli: rework git-backport
• c2e2ade: pr: add /clean command
• ab4c1f1: Initial version of census upgrade bot
• a8fe187: 574: git-info should use info from commit notifications

Your commit was automatically rebased without conflicts.

Pushed as commit 4857968.

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