For MDN we’re using v2.5 to label just new issues (not to re-label existing ones) and it works as expected almost all the time — but occasionally it will unexpectedly remove a label it has just added.
mdn/content#16309 (comment) is an example.
The relevant config files are here:
https://gist.github.com/sideshowbarker/c25f8f87747c68d0409c14db9b56bcd9 is a copy of the raw log for the workflow run.
In looking at that log, I notice that while there’s an event logged for when the expected label is added, there’s actually no event logged that shows it being removed.
Note that in addition to github/issue-labeler, we also run andymckay/labeler, to do just one thing: add a needs-triage label.
The config file for that is at https://github.com/mdn/content/blob/main/.github/workflows/new-issues.yml
For MDN we’re using v2.5 to label just new issues (not to re-label existing ones) and it works as expected almost all the time — but occasionally it will unexpectedly remove a label it has just added.
mdn/content#16309 (comment) is an example.
The relevant config files are here:
https://gist.github.com/sideshowbarker/c25f8f87747c68d0409c14db9b56bcd9 is a copy of the raw log for the workflow run.
In looking at that log, I notice that while there’s an event logged for when the expected label is added, there’s actually no event logged that shows it being removed.
Note that in addition to github/issue-labeler, we also run andymckay/labeler, to do just one thing: add a
needs-triagelabel.The config file for that is at https://github.com/mdn/content/blob/main/.github/workflows/new-issues.yml