-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
[Bug]: Labels with emoji and space are not supported #461
Comments
I tried hacking around the issue using quotes, replacing: pr_labels: 📚 documentation with: pr_labels: '📚 documentation' But it still fails:
|
Double quoting doesn't work either: pr_labels: "📚 documentation"
|
Hi @kdeldycke and thank you for the bug report. Following lines are responsible (Currently I think the rest of the code should handle labels containing emojis with space): function maybe_create_labels () {
all_labels=${PR_LABELS//,/$'\n'}
for label in $all_labels
do e.g. with PR_LABELS=""📚 documentation, <next_labels>" (next_labels can be empty) the related for loop will first take Trying to solve this issue ASAP. (cannot promise today) Remark but you need to manually add the label to the repository. (automatic add of a label to the repo has been added with #438). As said above I will try to solve the issue soon (next days) |
@all-contributors please add @kdeldycke for bug |
I've put up a pull request to add @kdeldycke! 🎉 |
@kdeldycke #462 will fix the bug. Tested with Please update to Please get back if you still face issues. |
Thanks for the really fast fix! Just updated my workflows, I'll certainly have the confirmation soon that everything's fine with v1.6.2. |
Just confirmed v1.6.2 fixed my issue! See: kdeldycke/awesome-engineering-team-management#90 |
Is there an existing issue for this?
Describe the bug
Hi have a step that looks like this:
(source)
This fails because the label contains emoji.
Expected Behavior
I would like
actions-template-sync
to be able to label PRs it creates with labels containing emojis and spaces.Current Behavior
With the YAML configured as above with emoji, the action ends up with this issue:
Steps To Reproduce
No response
Possible Solution
No response
Additional Information/Context
No response
Template sync version Version
1.6.0
The text was updated successfully, but these errors were encountered: