616: Sponsorship information is incorrect.

[rwestberg]

In the "this PR requires a sponsor" message, there's no need to display different messages depending on author status, just say that Committer status is required.

Best regards,
Robin

---

Progress

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

Issue

• SKARA-616: Sponsorship information is incorrect.

Reviewers

• Erik Helin (@edvbld - Reviewer)

Download

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

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

[openjdk]

@rwestberg The following label will be automatically applied to this pull request: bots.

When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label (add|remove) "label" command.

[mlbridge]

Webrevs

• 01: Full - Incremental (e00e958)
• 00: Full (fc35c49)

[edvbld]

Can we make project a link to the project in https://openjdk.java.net/census ?

[edvbld]

Looks great!

[openjdk]

@rwestberg This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements

After integration, the commit message will be:

616: Sponsorship information is incorrect.

Reviewed-by: ehelin

• If you would like to add a summary, use the /summary command.
• To credit additional contributors, use the /contributor command.
• To add additional solved issues, use the /issue command.

Since the source branch of this PR was last updated there have been 4 commits pushed to the master branch:

• de0ffaa: 634: Refresh PR data between commands in CommandWorkItem
• fe45ab0: 598: Add test-request label when test request needs approval
• 985532d: jira: make links() more reliable
• ab9de3d: 625: Proxy build plugin should work on URLs without scheme

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge master into your branch, and then specify the current head hash when integrating, like this: /integrate de0ffaa7590811cf4d10ba16d1d5de3cf56c5beb.

➡️ 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 4 commits pushed to the master branch:

• de0ffaa: 634: Refresh PR data between commands in CommandWorkItem
• fe45ab0: 598: Add test-request label when test request needs approval
• 985532d: jira: make links() more reliable
• ab9de3d: 625: Proxy build plugin should work on URLs without scheme

Your commit was automatically rebased without conflicts.

Pushed as commit 8806fe5.

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