Package Exports

backport

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (backport) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

backport

A simple CLI tool that automates the process of backporting commits

Demonstration gif

What is backporting?

Backporting is the action of taking parts from a newer version of a software system [..] and porting them to an older version of the same software. It forms part of the maintenance step in a software development process, and it is commonly used for fixing security issues in older versions of the software and also for providing new features to older versions.

Source: https://en.wikipedia.org/wiki/Backporting

Who is this tool for?

This tools is for anybody who is working on a codebase where they have to maintain multiple versions. If you manually cherry-pick commits from master and apply them to one or more branches, this tool might save you a lot of time.

backport is a CLI that will ask you which commit(s) to backport and to which branch(es) and then cherry-pick accordingly, and create pull requests. It will always perform the git operation in a temporary folder (~/.backport/repositories/) separate from your working directory, thus never interfering with any unstages changes your might have.

Features:

interactively backport one or more commits to one or more branches with an intuitive UI
backport a commit by specifying a PR (--pr 1337)
list and backport commits by a particular user (--author john)
list and backport commits by a particular path (--path src/plugins/chatbot)
see which commits have been backported and to which branches
add a custom title, description and labels to the created backport PR

Requirements

Node 8 or higher
git

Docker

Install with Node (recommended)

npm install -g backport

After installation you should update the global config in ~/.backport/config.json with your Github username and a Github access token.

Run via Docker

If you don't have Node.js or git installed locally, you can run backport via Docker.

Click to expand

The easiest way is to add the following snippet to your bash profile:

backport() {
    BACKPORT_CONFIG_DIR=~/.backport
    GIT_CONFIG_FILE=~/.gitconfig

    docker run -it --rm -v $(pwd):/app:ro -v $BACKPORT_CONFIG_DIR:/root/.backport -v $GIT_CONFIG_FILE:/etc/gitconfig sqren/backport "$@"
}

Where:

BACKPORT_CONFIG_DIR: This can be ANY empty folder on your local machine. Upon running the docker container for the first time, a config.json will be created automatically. This must be filled out with username and accessToken or these must be passed as CLI arguments: backport --username <username> --accessToken <accessToken>
GIT_CONFIG_FILE: Must point to a local .gitconfig file that contains the user's name and email.

You can now use backport as if it was installed on the host machine.

Usage

Run the CLI in your project folder (must contain a .backportrc.json file):

> backport

or run this from anywhere:

> backport --upstream elastic/kibana

The above commands will start an interactive prompt. You can use the arrow keys to choose options, <space> to select checkboxes and <enter> to proceed.

CLI arguments

Option	Description	Default	Type
--accesstoken	Github access token		string
--all	Show commits from other than me	false	boolean
--api-hostname	Hostname for the Github API	api.github.com	string
--author	Filter commits by author	Current user	string
--branch	Branch to backport to		string
--commits-count	Number of commits to choose from	10	number
--editor	Editor (eg. `code`) to open and solve conflicts		string
--fork	Create backports in fork (true) or origin repo (false)	true	boolean
--git-hostname	Hostname for Git remotes	github.com	string
--labels	Pull request labels		string
--multiple	Select multiple commits/branches	false	boolean
--path	Only list commits touching files under a specific path		string
--pr-description	Pull request description suffix		string
--pr-title	Pull request title pattern		string
--pr	Pull request to backport		number
--reset-author	Set yourself as commit author		boolean
--sha	Sha of commit to backport		string
--upstream	Name of organization and repository		string
--username	Github username		string
--help	Show help
-v, --version	Show version number

All of the CLI arguments can also be configured via the configuration options in the config files.

Contributing

See CONTRIBUTING.md