286: Add a link to CSR in the PR's first comment

[lgxbslgx]

Hi all,

This patch adds a link to the csr in the PR's first comment under Issue.
And the corresponding test is added.

Thanks for taking the time to review.

Best Regards,
-- Guoxiong

---

Progress

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

Issue

• SKARA-286: Add a link to CSR in the PR's first comment

Reviewers

• Magnus Ihse Bursie (@magicus - Reviewer) ⚠️ Review applies to c023b80
• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

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

Update a local copy of the PR:
$ git checkout pull/1244
$ git pull https://git.openjdk.java.net/skara pull/1244/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1244

View PR using the GUI difftool:
$ git pr show -t 1244

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/skara/pull/1244.diff

[bridgekeeper]

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

• 05: Full - Incremental (c8670301)
• 04: Full - Incremental (575de407)
• 03: Full - Incremental (19521b67)
• 02: Full - Incremental (2d7996ec)
• 01: Full - Incremental (55fc8dda)
• 00: Full (c023b808)

[magicus]

Looks good to me, but please await Erik's review as well.

[openjdk]

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

286: Add a link to CSR in the PR's first comment

Reviewed-by: ihse, erikj

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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 (@magicus, @erikj79) 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).

[lgxbslgx]

@magicus Thanks for your review. I updated the code to solve the null exception.

Also wait @erikj79 to review.

[erikj79]

Overall I like this change. I'm wondering if we should add something like "CSR" either before or after the CSR link to make it clearer what the issue link is. I would suggest a bold CSR within normal parentheses after the title. This matches the formatting of the reviewer attributions further down in the body.

[erikj79]

I don't think we should throw an exception here. If we do, then a bad state in JBS will completely prevent the PullRequestBot from updating the status of the affected PR. I would prefer logging a warning and returning Optional.empty().

[lgxbslgx]

Thanks for the review. I updated the code just now.

I would suggest a bold CSR within normal parentheses after the title.

Added.

I don't think we should throw an exception here

Fixed.

And I find the intergration blocker shouldn't invoke the method CheckRun#issues directly, so I add a parameter withCsr to the method CheckRun#issues to separate these two situations.

[erikj79]

Looks good!

[lgxbslgx]

@erikj79 @magicusThanks for the reviews. Could I get your help to sponsor this patch?

/integrate

[openjdk]

@lgxbslgx
Your change (at version 19521b6) is now ready to be sponsored by a Committer.

[lgxbslgx]

I updated the code to reduce the nested if statements and reduce the number of iterations in for statement.

[lgxbslgx]

/integrate

[openjdk]

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

[erikj79]

I can sponsor this.

[erikj79]

/sponsor

[openjdk]

Going to push as commit 43aedeb.

[openjdk]

@erikj79 @lgxbslgx Pushed as commit 43aedeb.

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