Page History

...

Requires that the pull requested has a JBS issue associated and that the JBS issue has a CSR request associated with it and that the CSR request is approved before the pull request can be integrated.

...

• /csr needed
• /csr unneeded
• /csr

/jep

Syntax

/jep [<issue-id>|JEP-<jep-id>|jep-<jep-id>|unneeded]

Description

Declares that this pull request is part of a JDK Enhancement Proposal. The linked JEP needs to be targeted before the pull request can be integrated. The command can be issued by the pull request author or a reviewer.

Examples

• /jep JDK-1234567
• /jep JEP-123
• /jep unneeded

/reviewer

Syntax

/reviewer (credit|remove) <username>[,<username>,...]

Description

Give additional users credit for reviewing a pull request. The usernames can either be a username of the source code hosting provider (e.g. a GitHub username) or an OpenJDK username. Note that not all OpenJDK projects allows the pull request author to credit additional reviewers. A reviewer credited via /reviewer credit will not count as a verified reviewer and some OpenJDK projects do not count unverified reviewers as enough for integration. A reviewer can be removed by issuing the /reviewer remove command.

Examples

• /reviewer credit @edvbld
• /reviewer credit ehelin
• /reviewer remove ehelin

/reviewers

Syntax

/reviewers N [role]


Description

Require that at least N users with given role (defaults to Author) review the pull request before it can be integrated. The requirements are in addition to the ones specified by the .jcheck/conf file. For example, if the .jcheck/conf file requires 1 Reviewer, then issuing the command "/reviewers 2" means that 1 Reviewer and 1 Author is required to integrate the pull request. Any additional invocations of this command completely supersedes any previous invocations.

Examples

• /reviewers 2
• /reviewers 3 reviewer

/label

Syntax

/label [add|remove] <label>[,<label>,...]


Alias

/cc


Description

Adds or removes labels on the pull request. If no action is specified, then the action defaults to "add". Labels have the same name as the development mailing lists without the -dev suffix, e.g. the label "hotspot" corresponds to the "hotspot-dev" mailing list. The mailing list bridge will send the RFR e-mail according to the labels on the pull request. Note that only labels associated with mailing lists can be controlled with this command and not Skara specific labels which are controlled by the bots or other specific commands (e.g. clean, rfr).

Examples

• /label add hotspot
• /label remove build,core-libs
• /label client
• /cc hotspot-gc hotspot-runtime
• /cc core-libs

/clean

Syntax

/clean

Description

Marks a backport pull request as clean. Skara will attempt to automatically determine if a backport pull request is a clean backport, but sometimes this automatic check fails even if the pull request could be considered clean.

/open

Syntax

/open

Description

If a pull request is automatically closed due to inactivity, this command can be used to re-open it.

/help

Syntax

/help

Description

Shows help for all pull request commands.

Examples

• /help