Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport a merged PR #11

Closed
korthout opened this issue Mar 23, 2021 · 1 comment
Closed

Backport a merged PR #11

korthout opened this issue Mar 23, 2021 · 1 comment
Assignees

Comments

@korthout
Copy link
Owner

Currently the backport action only supports backporting as part of the merge event of the PR. However, sometimes you forgot to backport a PR or the need to backport it arrises after the PR was already merged. Backporting a merged PR should be supported.

To trigger the backport we can consider that the user writes a comment like /backport. Labels can still be used to define which branches to backport the PR onto.

@korthout korthout self-assigned this Mar 30, 2021
@korthout
Copy link
Owner Author

Fixed with #14

ghost pushed a commit to camunda/camunda that referenced this issue May 14, 2021
7037: Add on-comment trigger to backport action workflow r=korthout a=korthout

## Description

Adds a workflow configuration to trigger the backport action
when a user writes a `/backport` comment on a pull request.
The bot itself restricts that only merged pull requests can be
backported.

This allows to backport pull requests that have already been merged.
Just add the backport labels to the merged PR and write `/backport`.

> WARNING! The bot will try to backport to the branches of all backport labels. 
> Previously created backport pull requests are not taken into account. 
> New pull requests will be created for each label.

## Related issues

<!-- Which issues are closed by this PR or are related -->

relates to korthout/backport-action#11



Co-authored-by: Nico Korthout <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant