Date: Fri, 29 Mar 2024 06:04:50 +0000 (UTC) Message-ID: <1391723574.1279.1711692290987@34fc92c9345b> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1278_1884643715.1711692290987" ------=_Part_1278_1884643715.1711692290987 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Project Skara provides committers with additional commit command= s that enable additional functionality. A commit command is a comm= ent 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 amoun= t of whitespace in front of it, but it must be the first non whitespace cha= racters 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 com= ment. 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 com= mand and not the Gitlab variant, you can put some whitespace in front of th= e command in the comment. Also, you can prepend "/skara" as a prefix to the= command. For instance, to execute the "/tag" command, you can use "/= skara tag 1.1", it will be interpreted as "/tag 1.1" by SKARA bot. The comm= and that currently conflict with GitLab commands is /tag.
Commands
/backport <repo> [<branch>]
/backport [<repo>]:<branch>
Applies the commit onto the given branch in the given repository and the= n shows to a link to create a pull request with the changes. In the first s= yntax, 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 same re= pository where the command is issued is used. 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 backpor=
t command by supplying the appropriate pr/X
branch.
The pull request will be created f= rom a branch in a shared fork of the target repository. On GitHub, this rep= ository is owned by the openjdk-bots organization. The first time you issue= the /backport command for a specific target repository, you will receive a= n invitation to collaborate in the fork repository. This invitation needs t= o be accepted to be able to further update the backport pull request with m= ore changes.
/tag <name>
Creates a tag for the commit with the given name. Note that only integra= tors in a repository are allowed to use this command. To become an integrat= or, file a Skara admin task issue explaining why.
/tag jdk-16+22
/tag 15.0.1+1
/branch <name>
Creates a new branch with the given name, starting at the commit. Note t= hat only integrators in a repository are allowed to use this command. To be= come an integrator, file a Skara admin task issue explaining why.
/branch jdk22.0.1
/help
Shows help for all commit commands.
/help