Initial implementation of dependent pull requests

[rwestberg]

This is the initial implementation of the support for creating a follow-up pull request while the first one is still out for review. This will allow having multiple dependent changes out for review simultaneously, which is something that was possible during the hg/webrev era.

To use it, first create a pull request from the first change. In that pull request, issue the /preintegrate command. This will publish the current contents to a new branch in the target repository named pr/<username>/<pr-id>. Now any follow-up work can target this branch instead, which contains the dependent work.

When the first pull request is /integrated, any follow-up pull requests will automatically be retargeted to the original target branch. It will not be possible to /integrate the follow-up pull request until the first one has been integrated.

---

Progress

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

Testing

	Linux x64	Windows x64	macOS x64
Build / test	⏳ (1/1 running)	✔️ (1/1 passed)	⏳ (1/1 running)

Reviewers

• Erik Helin (@edvbld - Reviewer) ⚠️ Review applies to 45ca450

Download

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

[bridgekeeper]

👋 Welcome back rwestberg! 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

• 02: Full - Incremental (0d849bb)
• 01: Full - Incremental (45ca450)
• 00: Full (24270bf)

[edvbld]

Looks good!

[openjdk]

@rwestberg 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:

Initial implementation of dependent pull requests

Reviewed-by: ehelin

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 3 new commits pushed to the master branch:

• 7774dcd: pr: detect clean backports
• 997d6db: jcheck: conditionally check backport reviewers
• e693901: git-info: add --upstream flag

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.

[rwestberg]

/integrate

[openjdk]

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

• 7774dcd: pr: detect clean backports
• 997d6db: jcheck: conditionally check backport reviewers
• e693901: git-info: add --upstream flag

Your commit was automatically rebased without conflicts.

Pushed as commit f38ef5a.

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