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
+59 −0
Merged

Adding labels to .github/settings.yml #86

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dd287ab
adding labels to .github/settings.yml
nate-double-u Jul 23, 2021
81bbf2e
Updating labels description comment
nate-double-u Jul 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
59 changes: 59 additions & 0 deletions .github/settings.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,62 @@ collaborators:
permission: admin
- username: kapunahelewong
permission: admin

# Labels: define labels for Issues and Pull Requests
labels:
- name: cleanup
color: 1ebcd8
- name: e1-hours
description: "Effort: < 8 hrs"
color: d9b38c
- name: e2-days
description: "Effort: < 5 days"
color: cc9966
- name: e3-weeks
description: "Effort: < 4 weeks"
color: bf8040
- name: e4-months
description: "Effort: 1+ months"
color: 996633
- name: infrastructure
color: 696969
- name: p0-critical
color: B60205
- name: p1-high
color: D93F0B
- name: p2-medium
color: FBCA04
- name: p3-low
color: FEF2C0
- name: e0-minutes
description: "Effort: < 60 min"
color: e6ccb3
# GitHub default labels
- 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).

description: Improvements or additions to documentation
color: 0075ca
- name: duplicate
description: This issue or pull request already exists
color: cfd3d7
- name: enhancement
description: New feature or request
color: a2eeef
- name: good first issue
description: Good for newcomers
color: 7057ff
- name: help wanted
description: Extra attention is needed
color: 008672
- name: invalid
description: "This doesn't seem right"
nate-double-u marked this conversation as resolved.
Show resolved Hide resolved
color: e4e669
- name: question
description: Further information is requested
color: d876e3
- name: wontfix
description: This will not be worked on
color: ffffff