Update managing-labels.md#39827
Conversation
Clarifying that labels are unique to a repo.
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
Outdated
Show resolved
Hide resolved
content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
Outdated
Show resolved
Hide resolved
content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
Outdated
Show resolved
Hide resolved
|
@dlheide This seems like a valid addition, and I think you've put it in a good place. I'll get it merged once checks are passing. |
content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
Outdated
Show resolved
Hide resolved
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Clarifying that labels are unique to a repo.
Why:
Closes: main...dlheide:docs:patch-1
What's being changed (if available, include any code snippets, screenshots, or gifs):
This page suggests that labels are unique to a repo. Empirical tests seem to support this. Adding text to clarify this.
Check off the following: