• Home
    • View
    • Login
    This page
    • Normal
    • Export PDF
    • Page Information

    Loading...
  1. Dashboard
  2. Undefined Space
  3. Skara
  4. Pull Request Commands

Page History

Versions Compared

Old Version 29

changes.mady.by.user Erik Helin

Saved on Sep 17, 2020

compared with

New Version 30

changes.mady.by.user Erik Helin

Saved on Oct 05, 2020

  • Previous Change: Difference between versions 28 and 29
  • Next Change: Difference between versions 30 and 31
  • View Page History

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Description

Marks the pull request as 'Reviewed-by' one or more users specified by the given usernamesGive 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.

...

  • /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.

Examples

  • /reviewers 2

/label

Syntax

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

Alias(es)

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

Examples

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

/help

Syntax

/help

Description

Shows help for all pull request commands.

Examples

  • /help
Overview
Content Tools
ThemeBuilder

Terms of Use
• License: GPLv2
• Privacy • Trademarks • Contact Us

Powered by a free Atlassian Confluence Open Source Project License granted to https://www.atlassian.com/software/views/opensource-community-additional-license-offer. Evaluate Confluence today.

  • Kolekti ThemeBuilder Powered by Atlassian Confluence 8.5.23
  • Kolekti ThemeBuilder printed.by.atlassian.confluence
  • Report a bug
  • Atlassian News
Atlassian
Kolekti ThemeBuilder EngineAtlassian Confluence
{"serverDuration": 237, "requestCorrelationId": "5278334320fad886"}