Skip to content
forked from tibdex/backport

🔙 GitHub Action to backport pull requests

License

Notifications You must be signed in to change notification settings

VachaShah/backport

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

70 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Fork

This is a managed fork of tibdex/backport.

Backport is a JavaScript GitHub Action to backport a pull request by simply adding a label to it.

It can backport rebased and merged pull requests with a single commit and squashed and merged pull requests. It thus integrates well with Autosquash.

Usage

  1. 🔌 Add this .github/workflows/backport.yml to your repository.

  2. 💬 Let's say you want to backport a pull request on a branch named production.

    Then label it with backport production. (See how to create labels.)

  3. ✨ That's it! When the pull request gets merged, it will be backported to the production branch. If the pull request cannot be backported, a comment explaining why will automatically be posted.

Note: multiple backport labels can be added. For example, if a pull request has the labels backport staging and backport production it will be backported to both branches: staging and production.

Features

This fork has some new features on top of the original Github Action. Following is a list of new features and how to use them:

  1. files_to_skip: This optional input option can be added to the Github Action in order to pass a list of files that can be skipped during backport.
  2. failure_labels: This optional parameter can be used to provide a comma seperated list of labels that get added to PRs with failing backports.

About

🔙 GitHub Action to backport pull requests

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 84.8%
  • JavaScript 15.2%