Commit Commands

Project Skara provides committers with additional commit commands that enable additional functionality. A commit command is a comment made to a commit that starts with a slash ("/"), for example "/tag" or "/backport". The command may appear on any line and with an arbitrary amount of whitespace in front of it, but it must be the first non whitespace characters that appear on a particular line.

Skara will only evaluate a given command once, so if you make a mistake and get an error message back, you need to enter a new command in a new comment. Editing the previous comment will not have any effect.

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.

Commands

/backport

Syntax

/backport <repo> [<branch>]

Description

Applies the commit onto the given branch in the given repository and then shows to a link to create a pull request with the changes. The branch is optional and defaults to the master branch. If the commit does not apply then a message is shown describing the files containing conflicts. 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. 

Examples

• /backport jdk16u
• /backport jfx jfx14
• /backport jdk17u-dev pr/4711

/tag

Syntax

/tag <name>

Description

Creates a tag for the commit with the given name. Note that only integrators in a repository are allowed to use this command. To become an integrator, file a Skara admin task issue explaining why.

Examples

• /tag jdk-16+22
• /tag 15.0.1+1

/help

Syntax

/help

Description

Shows help for all commit commands.

Examples

• /help