-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add omit-labels
functionality [DOC-268]
#15
base: master
Are you sure you want to change the base?
Conversation
When backports are triggered via PR labels, copying the labels to the backport PRs can cause an unexpected cascade. E.G.: - a PR is labelled to backport to multiple branches - an action performs these actions _in parallel_ - the backported, labelled PRs are detected - more backporting is performed - etc Instead it would be easier to _optionally_ omit copying labels to backported PRs. Fixes: [DOC-268](https://hazelcast.atlassian.net/browse/DOC-268)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to omit labels completely when the backport is triggered by the label?
I don’t think I can detect that - in |
I mean what's your plan for fixing this issue on the workflow side? |
I don't have one. You can see my idea here. Ideas welcomed. |
Sorry, I can't see where's the loop? The workflow is triggered by |
There's an inverse action that forwardports commits to Even if it's not possible today, labels aren't really used in |
When backports are triggered via PR labels, copying the labels to the backport PRs can cause an unexpected cascade.
E.G.:
Instead it would be easier to optionally omit copying labels to backported PRs.
Fixes: DOC-268