SKARA-725: Rename git-pr-reviewer --add to git-pr-reviewer --credit

[amCap1712]

Hi!
The patch renames the add option to the credit in accordance with the change in the /reviewer command on OpenJDK Github bot.

I was unable to find any related documentation that should reflect this change. If something needs to be updated, kindly point me to it and I'll do the needful changes.

Thanks.
Regards,
Kartik

---

Progress

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

Issue

• SKARA-725: Rename git-pr-reviewer --add to git-pr-reviewer --credit

Reviewers

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

Download

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

[bridgekeeper]

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

• 01: Full - Incremental (f9b5ce9)
• 00: Full (e6dfcc8)

[mlbridge]

Mailing list message from David Holmes on skara-dev:

Hi,

On 3/11/2020 3:27 am, Kartik Ohri wrote:

Hi!
The patch renames the add option to the credit in accordance with the change in the `/reviewer` command on OpenJDK Github bot.

I was unable to find any related documentation that should reflect this change. If something needs to be updated, kindly point me to it and I'll do the needful changes.

Documentation is here:

https://wiki.openjdk.java.net/display/SKARA/Pull+Request+Commands#PullRequestCommands-/reviewer

Cheers,
David

[amCap1712]

Thanks David for the reply. I think the link you mentioned is rather for the PR bot not the cli tool. But in any case, I do not have a OpenJDK login so I think cannot modify that page.

[edvbld]

Looks good, just a small suggestion on the helptext for the option. I updated the documentation at https://wiki.openjdk.java.net/display/SKARA/reviewer.

[openjdk]

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

725: Rename git-pr-reviewer --add to git-pr-reviewer --credit

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

• 38aa5bf: Only consider resolved backports when applying sync label
• 0a8b1e7: vcs: add DiffComparator for comparing diffs
• 2e35aff: pr: return HostedCommit from CheckRun.backportedFrom
• 4f35b6f: cli: add command git-backport
• 4afd995: Restrict merge PR commit titles if required by the jcheck configuration
• c73f2b0: Run skara pre-submit tests against the latest commit on the target branch
• dd7933b: forge: return commit comment from addCommitComment
• 9a725bb: pr: add /backport commit command
• 4d7471a: 768: Skara bot should prevent attempt to use JBS backport issue ID in PR
• 5045eeb: Allow targeting non-open issues with the label command
• ... and 4 more: https://git.openjdk.java.net/skara/compare/d2401270372fbf2ce5126d1113cc0705c6e9139b...master

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 (@edvbld) 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).

[amCap1712]

/integrate

[openjdk]

@amCap1712
Your change (at version f9b5ce9) is now ready to be sponsored by a Committer.

[edvbld]

/sponsor

[openjdk]

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

• 38aa5bf: Only consider resolved backports when applying sync label
• 0a8b1e7: vcs: add DiffComparator for comparing diffs
• 2e35aff: pr: return HostedCommit from CheckRun.backportedFrom
• 4f35b6f: cli: add command git-backport
• 4afd995: Restrict merge PR commit titles if required by the jcheck configuration
• c73f2b0: Run skara pre-submit tests against the latest commit on the target branch
• dd7933b: forge: return commit comment from addCommitComment
• 9a725bb: pr: add /backport commit command
• 4d7471a: 768: Skara bot should prevent attempt to use JBS backport issue ID in PR
• 5045eeb: Allow targeting non-open issues with the label command
• ... and 4 more: https://git.openjdk.java.net/skara/compare/d2401270372fbf2ce5126d1113cc0705c6e9139b...master

Your commit was automatically rebased without conflicts.

Pushed as commit f4dc83b.

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