What is the difference between the use cases for the repo s

Question

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

bitter-ability-32190 · Answer

The category tags were introduced to categorize PRs I suspect the `documentation` tag predates that change and tagged issues

busy-vase-39202 · Answer

So I can safely ignore it correct Always use `category documentation`

bitter-ability-32190 · Answer

In PRs yeah

busy-vase-39202 · Answer

Is there ever a time when it s appropriate in Issues either I m opening several devrel issues some of which are documentation related

bitter-ability-32190 · Answer

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

busy-vase-39202 · Answer

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` woman shrugging

bitter-ability-32190 · Answer

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 man shrugging

busy-vase-39202 · Answer

Yeah

bitter-ability-32190 · Answer

Issue tags are freeform for human categorization PR tags are scoped and for script categorization If that helps the way to look at it

bitter-ability-32190 · Answer

There s nothing saying we couldn t develop a policy where the two are joined

busy-vase-39202 · Answer

It does

bitter-ability-32190 · Answer

I do wish we had the bandwidth and energy for better policies discipline

busy-vase-39202 · Answer

i think this is more of just a documentation issue

bitter-ability-32190 · Answer

ironic

busy-vase-39202 · Answer

haha

curved-television-6568 · Answer

agree with the above `category ` tags for PRs only

bitter-ability-32190 · Answer

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

happy-kitchen-89482 · Answer

We could get rid of `documentation` `category ` are for classifying the changelog but they can also serve the regular purpose of a label

bitter-ability-32190 · Answer

I think I asked this question a while ago thinking face I don t remember the outcome

busy-vase-39202 · Answer

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

busy-vase-39202 · Answer

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