https://pantsbuild.org/ logo
b

busy-vase-39202

05/02/2023, 4:28 PM
What is the difference between the use cases for the repo's
documentation
and
category:documentation
tags? I have always used the latter for docs changes and am not certain under what circumstances the former should be used instead.
b

bitter-ability-32190

05/02/2023, 4:28 PM
The category tags were introduced to categorize PRs. I suspect the
documentation
tag predates that change and tagged issues
b

busy-vase-39202

05/02/2023, 4:37 PM
So I can safely ignore it, correct? Always use
category:documentation
?
b

bitter-ability-32190

05/02/2023, 4:38 PM
In PRs? yeah
b

busy-vase-39202

05/02/2023, 4:40 PM
Is there ever a time when it's appropriate in Issues either? I'm opening several devrel issues, some of which are documentation-related.
b

bitter-ability-32190

05/02/2023, 4:41 PM
Yeah I'd maybe use the
documentation
tag for that one. Not saying it's an ideal situation. It's just the situation I see us in
b

busy-vase-39202

05/02/2023, 4:43 PM
Should I use both tags on issues, or prefer
documentation
? It seems odd that a PR meant to resolve a
documentation
issue would be tagged
category:documentation
. 🤷‍♀️
b

bitter-ability-32190

05/02/2023, 4:45 PM
I would personally use
documentation
. The category labels are for PR classification primarily. Again, this is a crossroads of tags-for-people and tags-for-automation 🤷‍♂️
b

busy-vase-39202

05/02/2023, 4:46 PM
Yeah.
b

bitter-ability-32190

05/02/2023, 4:46 PM
Issue tags are freeform for human categorization. PR tags are scoped and for script categorization. If that helps the way to look at it
There's nothing saying we couldn't develop a policy where the two are joined
b

busy-vase-39202

05/02/2023, 4:46 PM
It does!
b

bitter-ability-32190

05/02/2023, 4:47 PM
I do wish we had the bandwidth and energy for better policies/discipline
b

busy-vase-39202

05/02/2023, 4:47 PM
i think this is more of just a documentation issue.
b

bitter-ability-32190

05/02/2023, 4:47 PM
ironic
b

busy-vase-39202

05/02/2023, 4:47 PM
haha
c

curved-television-6568

05/02/2023, 5:55 PM
agree with the above,
category:..
tags for PRs only.
b

bitter-ability-32190

05/02/2023, 5:56 PM
I could see in the future, using a system of tagging for issues too. And the PR inherits the tags of the issue(s) it fixes. Baby steppies
👍 1
h

happy-kitchen-89482

05/02/2023, 5:59 PM
We could get rid of
documentation
.
category:*
are for classifying the changelog, but they can also serve the regular purpose of a label.
b

bitter-ability-32190

05/02/2023, 5:59 PM
I think I asked this question a while ago 🤔 I don't remember the outcome
b

busy-vase-39202

05/02/2023, 7:03 PM
If we can safely get rid of it and any other seeming dupes, I suspect it would help gain more compliance with the CI requirement for labeling.
For someone not sure which label to choose, the safe choice is to leave that work to more knowledgable people. So disambiguating frees a few more people to do the step.
3 Views