pr: configure fork names explicitly

[edvbld]

Hi all,

please review this small patch that allows fork names to be configured a bit more freely for the PR bot.

Thanks,
Erik

---

Progress

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

Reviewers

• Robin Westberg (@rwestberg - Reviewer)

Download

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

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

[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: configure fork names explicitly

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

• 5707318: Avoid considering fixVersions that are not valid releases when calculating the hgupdate-sync label
• ef5e027: 893: Skara has no mailing list rule for some macOS native client code

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.

[mlbridge]

Webrevs

• 00: Full (88f8b64)

[edvbld]

/integrate

[openjdk]

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

• 56221f3: forge: double time-span for recent commit comments for GitLab
• 47b06d0: cli: add debug command commit-comments
• 5707318: Avoid considering fixVersions that are not valid releases when calculating the hgupdate-sync label
• ef5e027: 893: Skara has no mailing list rule for some macOS native client code

Your commit was automatically rebased without conflicts.

Pushed as commit 3cf5bd0.

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