744: The "Webrevs" link in the PR has confusing link to the changes for just one commit

[edvbld]

Hi all,

please review this pull request that makes the link to the commit after the webrev be a bit more useful. Previously we relied on the forge to "do the right thing" we it noticed a full hash to a commit (link to the changes). This worked fine on GitLab but didn't work as well on GitHub. I have now introduced a proper abstraction and use that to provide the same link on GitLab but a better link on GitHub.

Thanks,
Erik

---

Progress

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

Issue

• SKARA-744: The "Webrevs" link in the PR has confusing link to the changes for just one commit

Reviewers

• Robin Westberg (@rwestberg - Reviewer)

Download

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

To update a local copy of the PR:
$ git checkout pull/1077
$ git pull https://git.openjdk.java.net/skara pull/1077/head

[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 (3197bbd)

[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:

744: The "Webrevs" link in the PR has confusing link to the changes for just one commit

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

• 60eb3a6: cli: add --atomic and --manual to git-pr-integrate
• e6502c8: 757: git webrev with file list fails if any file has not changed
• fedf7ad: 823: git fork --setup-pre-push-hook => FAIL

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

• 60eb3a6: cli: add --atomic and --manual to git-pr-integrate
• e6502c8: 757: git webrev with file list fails if any file has not changed
• fedf7ad: 823: git fork --setup-pre-push-hook => FAIL

Your commit was automatically rebased without conflicts.

Pushed as commit f16663b.

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