-
Notifications
You must be signed in to change notification settings - Fork 29
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
Copy labels as specified by copy_labels_pattern #314
Conversation
|
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.
Thanks so much @lheckemann 🚀 Such a cool feature. I'm sure my team wants to use this as well.
🙇 I have 2 small change requests, and then we should be able to merge this. Let me know if you want to apply these, or whether I should take it over. Happy to do so.
I tried rebasing on main to fix the merge conflict, but it appears that
main
doesn't currently build
The exaca
dependency was updated to a new major version with a breaking change (the import is now named, instead of default). Running npm ci
locally should solve the issue for you. You can then build a new version with npm run all
.
# Regex pattern to match github labels which will be copied from the | ||
# original PR to the backport PR. |
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.
Let's clarify what happens to the backport labels. Also please note that the documentation generally uses the term pull request
over PR
.
# Regex pattern to match github labels which will be copied from the | |
# original PR to the backport PR. | |
# Regex pattern to match github labels which will be copied from the | |
# original pull request to the backport pull request. Labels matching | |
# `label_pattern` will not be copied. |
Please also apply these changes to action.yml
# Optional | ||
# Regex pattern to match github labels which will be copied from the | ||
# original PR to the backport PR. | ||
# copy_labels_pattern: ^severity.* |
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.
The examples show the default value. I'd like to continue that.
# copy_labels_pattern: ^severity.* | |
# copy_labels_pattern: null |
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.
Can we still put a "useful" example somewhere visible?
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.
Sure. How about in the comment which describes the field?
@lheckemann Would you like me to take it over from here, or do you want to work on the requested changes yourself? |
I noticed another problem: the default of |
My apologies, @lheckemann. I've prioritized #317 because it was already fully functional (and smaller in scope). I'll be out of the office next week, but I'll continue with this pull request as soon as I find the time again. |
@lheckemann I finally found some time to look into this. I've just pushed a new branch Next, I want to run some tests with this to see if all works well. But it looks good so far! 🎉 Thanks again for this! |
Oh, that's a simple solution! Thanks for taking care of it. |
Just finished testing ✅ I needed to make a few small adjustments, but it works: Case 1
Case 2:
I'll clean up the commits and open a new PR (as I cannot edit this one). |
I had to shift focus a bit before I could release it, but it's released in Thanks again for all your efforts @lheckemann 🥇 |
Fixes #87