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

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

Page History

Versions Compared

Old Version 65

changes.mady.by.user Erik Joelsson

Saved on Oct 19, 2023

compared with

New Version Current

changes.mady.by.user Erik Joelsson

Saved on May 14, 2025

  • Previous Change: Difference between versions 64 and 65
  • View Page History

Key

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

...

Note that if you are using Skara on Gitlab, there are built in commands that clash with some of the Skara commands. To enforce use of the Skara command and not the Gitlab variant, you can put some whitespace in front of the command in the comment. Also, you can prepend "/skara" as a prefix to the command. For instance, to execute the "/label" command,  you can use "/skara label hotspot", it will be interpreted as "/label hotspot" by SKARA bot. The commands that currently conflict with GitLab commands are /reviewer, /label and /approve.

...

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

/backport

Syntax

/backport <repository> [<branch>disable] <repo> [<branch>]

/backport [disable <repository> ] [<repo>]:<branch>] 

Description

/backport used in open pull request

...

Applies the commit this pull request resulted in onto the given branch in the given repository and then shows to a link to create a pull request with the changes. The In the first syntax, the branch is optional, if not given, the default for the repository is used. In the second syntax, repo is optional, if not given, the repository will be same repository where the command is issued is used. If the commit does not apply then a message is shown describing the files containing conflicts. See See Backports.

If the target repository is configured to support dependent pull requests, it's possible to do this with the backport command by supplying the appropriate pr/X branch.

The pull request will be created from a branch in a shared fork of the target repository. On GitHub, this repository is owned by the openjdk-bots organization. The first time you issue the /backport command for a specific target repository, you will receive an invitation to collaborate in the fork repository. This invitation needs to be accepted to be able to further update the backport pull request with more changes.

Examples

  • /backport :jdk23
  • /backport jdk16u
  • /backport jfx jfx14
  • /backport jdk17u-dev pr/47114711
  • /backport disable jdk16u
  • /backport jfx:jfx22
  • /backport disable :jfx22

/approval

Syntax

/approval [<id>] (request|cancel) [<text>]

...

  • /author set @openjdk-bot
  • /author @openjdk-bot
  • /author set J. Duke <duke@openjdk.org>
  • /author remove @openjdk-bot
  • /author remove

/touch

Syntax

/touch

Alias

/keepalive

Description

A no-op command that triggers a re-evaluation of the pull request and resets the timer for automatically closing a pull request due to inactivity. This command does not trigger sending of any emails.


/help

Syntax

/help

Description

Shows help for all pull request commands.

...

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": 204, "requestCorrelationId": "2b51b521215164a5"}