forked from go-gitea/gitea
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/main'
* upstream/main: (35 commits) Small refactor for loading PRs (go-gitea#22652) Allow setting access token scope by CLI (go-gitea#22648) Add main landmark to templates and adjust titles (go-gitea#22670) Fix cache-control header clearing comment text when editing issue (go-gitea#22604) Enable `@<user>`- completion popup on the release description textarea (go-gitea#22359) Add Conda package registry (go-gitea#22262) Add user secrets (go-gitea#22191) Add missing close bracket in imagediff (go-gitea#22710) Explain that the no-access team unit does not affect public repositories (go-gitea#22661) Fix bugs with WebAuthn preventing sign in and registration. (go-gitea#22651) Add more events details supports for actions (go-gitea#22680) Improve checkbox accessibility a bit by adding the title attribute (go-gitea#22593) Add repository setting to enable/disable releases unit (go-gitea#22671) Use relative url in actions view (go-gitea#22675) Fix ref to trigger Actions (go-gitea#22679) Rootless Docker - Mistake with the repo-avatars parent folder name (go-gitea#22637) Fix missing title and filter in issue sidebar project menu (go-gitea#22557) Fix wrong hint when deleting a branch successfully from pull request UI (go-gitea#22673) Add Contributed backport command (go-gitea#22643) Fix typo in command-line.en-us.md (go-gitea#22681) ...
- Loading branch information
Showing
352 changed files
with
10,129 additions
and
657 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
`backport` | ||
========== | ||
|
||
`backport` is a command to help create backports of PRs. It backports a | ||
provided PR from main on to a released version. | ||
|
||
It will create a backport branch, cherry-pick the PR's merge commit, adjust | ||
the commit message and then push this back up to your fork's remote. | ||
|
||
The default version will read from `docs/config.yml`. You can override this | ||
using the option `--version`. | ||
|
||
The upstream branches will be fetched, using the remote `origin`. This can | ||
be overrided using `--upstream`, and fetching can be avoided using | ||
`--no-fetch`. | ||
|
||
By default the branch created will be called `backport-$PR-$VERSION`. You | ||
can override this using the option `--backport-branch`. This branch will | ||
be created from `--release-branch` which is `release/$(VERSION)` | ||
by default and will be pulled from `$(UPSTREAM)`. | ||
|
||
The merge-commit as determined by the github API will be used as the SHA to | ||
cherry-pick. You can override this using `--cherry-pick`. | ||
|
||
The commit message will be amended to add the `Backport` header. | ||
`--no-amend-message` can be set to stop this from happening. | ||
|
||
If cherry-pick is successful the backported branch will be pushed up to your | ||
fork using your remote. These will be determined using `git remote -v`. You | ||
can set your fork name using `--fork-user` and your remote name using | ||
`--remote`. You can avoid pushing using `--no-push`. | ||
|
||
If the push is successful, `xdg-open` will be called to open a backport url. | ||
You can stop this using `--no-xdg-open`. | ||
|
||
Installation | ||
============ | ||
|
||
```bash | ||
go install contrib/backport/backport.go | ||
``` |
Oops, something went wrong.