• 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 53

changes.mady.by.user Zhao Song

Saved on Feb 06, 2023

compared with

New Version Current

changes.mady.by.user Zhao Song

Saved on May 10, 2023

  • Previous Change: Difference between versions 52 and 53
  • View Page History

Key

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

...

/integrate [auto|delegate|undelegate|manual|<hash>]

Description

The pull request command that all contributors will use is the /integrate command that integrates an approved pull request into a repository. This is an example where the Skara workflow differs slightly from the workflow offered by most external Git source code hosting providers - almost all external Git source code hosting providers require that a reviewer/maintainer integrates a pull request into a repository. Skara instead enables the contributor to integrate the pull request with the /integrate command, but the contributor can only issue the /integrate command once the pull request passes all pre-integration checks (e.g. jcheck).

...

The auto parameter is used to label a pull request to be automatically integrated as soon as all pre-integration checks are passing. This can be a good idea to save time when a change is comparatively benign and only the minimum amount of review is needed.

The manual parameter is used to undo the effects of the auto parameter.

If a contributor of a pull request will be unable to perform the integration at a suitable time, they may delegate the ability to integrate to any other committer in the project. This is done using /integrate delegate. Issuing this command will not immediately integrate a pull request, instead any committer in the project will be able to issue the /integrate command to perform the integration. This can be undone by the original contributor running /integrate undelegate.

...

/backport <repository> [<branch>]

Description

Now, /backport could only be /backport disable <repository> [<branch>] 

Description

/backport used in open pull request

When used in an open pull request, the /backport command adds a Backport=repo:branch label to the PR. After the PR is integrated, the bot will create the backport branch and provides a link for creating the backport. To cancel the backport, the user can use /backport disable command to remove the label before the PR is integrated.

Note: /backport disable can only be used in open pull requests.


/backport used in integrated 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 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.

...

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 7.19.6
  • Kolekti ThemeBuilder printed.by.atlassian.confluence
  • Report a bug
  • Atlassian News
Atlassian
Kolekti ThemeBuilder EngineAtlassian Confluence
{"serverDuration": 164, "requestCorrelationId": "926c3bae9c8c6fd7"}