Audit Website Team Labels
- Dominant language
- JavaScript
- Stars
- 363
- Forks
- 872
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 18
Description
### Dependency
- [x] #3636
- [x] #1534
- [ ] Relaunch of the new wiki
### Overview
As a developer, we need to ensure that our labels are up-to-date, removing unnecessary labels as required.
### Action Items
- [ ] Make an audit of all labels used by the website team. A work-in-progress audit can be seen [here](https://docs.google.com/spreadsheets/d/1jWVH-1QAgcaMd3BInWEW6Zaq-z9lN-C4qJ6I3mchfNs/edit#gid=958863193)
- [ ] For this audit, you can either create a new spreadsheet or reuse the one in-progress
- [ ] For each label, include its name, description (as seen on the [labels page](https://github.com/hackforla/website/labels?page=1&sort=name-asc)), whether or not they are [a GitHub default](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels#about-default-labels), their usage, and recommended changes to the label
- [ ] Viable changes include changes to name, color, description, or even deleting the label entirely.
- [ ] As part of the audit, look for all wikis related to labels and create new issues as needed to update those wikis.
- [ ] Release dependency on #1941
### Resources/Instructions
Note: To make it easier to generate a spreadsheet, feel free to use the [labels API ](https://docs.github.com/en/rest/reference/issues#list-labels-for-a-repository)to generate a CSV before uploading it to our drive.
[List of all labels](https://github.com/hackforla/website/labels?page=1&sort=name-asc)
[How to add status labels to issues](https://github.com/hackforla/website/wiki/How-to-add-status-labels-to-issues)
[About default labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels#about-default-labels)
[List labels for a repository](https://docs.github.com/en/rest/reference/issues#list-labels-for-a-repository)
Contributor guide
Assessment
This issue has not been assessed yet.