backport-action
backport-action copied to clipboard
korthout
Fast and flexible GitHub action to cherry-pick merged pull requests to selected branches
## Summary The goal of this PR is to allow creating draft PR for backport that resulted in merge conflict. Similar to #386 ### Consideration - New input was added...
This pull request is still a work in progress, but I wanted to share my first iteration to get feedback early on: 1. Whether it generally makes sense and if...
**Is your feature request related to a problem? Please describe.** backport doesn't always succeed, especially if the source and target have diverged, but it can still be useful to have...
**Is your feature request related to a problem? Please describe.** Most comments by the action for errors are unclear, unhelpful, and appear to come from nowhere. Example no permission to...
GitHub actions are not allowed to push changes to GitHub action workflow files. When you attempt to backport a pull request with this action that includes changes to a workflow...
**Is your feature request related to a problem? Please describe.** PRs created by the backport-action do not trigger the CI for the PR. Triggering the CI, especially for backports, is...
We should be able to simplify the manual instructions that are commented when the action is unable to backport the pull request (e.g. due to conflicts). - make sure the...
Some users want to automatically backport a pull request to a dynamically defined set of target branches. For example, in https://github.com/korthout/backport-action/issues/343 the request was to backport to all branches matching...
I noticed that pull requests created by the backport-action don't trigger the CI - e.g. #347 That is because by default the backport-action uses `GITHUB_TOKEN` which cannot trigger other workflows....
It would be useful to automatically add a label when the backport failed, to make it easier to track which backports need to be handled manually.
