This is out of scope for triagers but a bot is being developed between myself and Raphael, to manage labels among GitHub repositories.
One guideline is, when in doubt, ask first before adding/removing label, and don’t remove labels added by core devs.
Perhaps this need to be split to a new thread but I don’t have the ability to do that, perhaps one of the admins will do it
invalid: This can be automatically added by bedevere when people try to merge maintenance branch to the master branch. It can be manually added by us too if we deem it
invalid. The effect is, the PR won;t count towards user’s contribution during hacktoberfest.
DO-NOT-MERGE: a core dev would usually apply this label. miss-islington knows not to merge PRs with this label. I think it should be ok for triagers to add the “do-not-merge” label when necessary, but let’s not remove it if core dev has added the label. Hope this makes sense?
needs backport to X.Y: you’re right that it will trigger miss-islington to autobackport, however, miss-islington won’t be able to merge the backport PR unless approved by a core dev. I’m thinking that it is harmless for a triager to trigger the autobackport, if anything it can help speed up the process. But I’m open to be convinced otherwise on this.
sprint: added when the PR was created during in person sprint (e.g. at PyCons, at EuroPython, at core sprint, etc). The idea is to prioritize reviewing them during the sprint.
type-tests: auto added by bedevere when the PR contains only doc changes (rst) or only tests changes. People interested in reviewing docs or tests-related PRs can use the label to find PRs to review.
type-...: They’re manually added. No effect to bots. Should be fine for triagers to add these labels to help categorize PRs accordingly. And of course, we trust triagers not to abuse their ability.