Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Adding labels to .github/settings.yml #86

Merged
merged 2 commits into from
Jul 26, 2021

Conversation

nate-double-u
Copy link
Member

@nate-double-u nate-double-u commented Jul 23, 2021

Fixes #79

Note: Adding labels this way will remove labels already added via the GitHub UI.

In case GitHub isn't able to reapply labels when merging this PR, this is how they are currently applied (to open issues/PRs):

bug: #56, #52, #45
cleanup: #85
documentation: #29, #24, #23, #22
enhancement: #83, #80, #28, #27, #26, #25, #21, #20, #19, #18
infrastructure: #85, #83, #79, #68
question: #76, #87

@nate-double-u
Copy link
Member Author

Are there other labels we want/need?

chalin
chalin previously approved these changes Jul 24, 2021
Copy link
Collaborator

@chalin chalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few tweaks (see inlined comments), but LGTM after that. Thanks!

.github/settings.yml Outdated Show resolved Hide resolved
- name: bug
description: "Something isn't working"
color: d73a4a
- name: documentation
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, let's drop this (like we did for etcd.io) -- since most PRs over a website repo will be for documentation (i.e., let's take that as the default when there's no extra label).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about that -- but as it is one of the default labels that GitHub creates on repo creation, I wonder if there is some value in keeping it (will template users expect it, even if we don't use it).

@chalin
Copy link
Collaborator

chalin commented Jul 24, 2021

Are there other labels we want/need?

Let's start with this very nice set.

kapunahelewong
kapunahelewong previously approved these changes Jul 26, 2021
Copy link
Contributor

@kapunahelewong kapunahelewong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

.github/settings.yml Show resolved Hide resolved
@nate-double-u
Copy link
Member Author

(latest force-push rebases the PR on main)

Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
@nate-double-u nate-double-u force-pushed the 79-adding-labels-github-settings branch from 0e1f735 to 81bbf2e Compare July 26, 2021 18:12
@nate-double-u nate-double-u merged commit 77b6f98 into main Jul 26, 2021
@nate-double-u nate-double-u deleted the 79-adding-labels-github-settings branch July 26, 2021 18:25
@nate-double-u
Copy link
Member Author

Nice, the existing label assignments were persevered.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add labels for effort, priority, infrastructure, cleanup/refactoring, etc
3 participants