Repository navigation
HIP 0005 - Structured Labels - #1978
yoshuawuyts wants to merge 5 commits into
Conversation
Signed-off-by: Yosh <github@yosh.is>
Add rollout plan for label migration and update label tagging guidelines. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Yosh <2467194+yoshuawuyts@users.noreply.github.com>
Signed-off-by: Yosh <github@yosh.is>
| | `area/testing` | `A-testing` | | ||
| | `github_actions` | `A-ci` | | ||
| | `good first issue` | `E-easy` | | ||
| | `Guest-COW` | `F-guest-cow` | |
There was a problem hiding this comment.
There are some in here like this that "acrue over time" I wouldn't say we need to retain all of these and I personally feel like less is more with these things so feel free to propose trimming things
There was a problem hiding this comment.
We do still have open issues with this tag + a number of historical ones. I agree less is more, but I also don't want to make too many changes at once - I kind of feel like I'm changing a fair bit already haha.
There was a problem hiding this comment.
I did see that we have a label archive feature; I'll make a comment that we should use that.
|
|
||
| ## Status quo | ||
|
|
||
| Hyperlight currently uses different labeling schemes across projects. Despite |
There was a problem hiding this comment.
There is tooling in github now that lets us set the same labels across the org. We should use that
jsturtevant
left a comment
There was a problem hiding this comment.
Pairing down to few labels would be nice to see IMO but over all this looks ok, particularly if we use agents to help do some of the triage and pull relevant information.
Just a heads up we do have some docs here on the process that was used previously https://github.com/hyperlight-dev/hyperlight/blob/main/docs/github-labels.md which we should make sure to update or document prior art
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Yosh <github@yosh.is>
This adds a proposal for reworking our use of GitHub labels, in particular to make it easier to create agendas, track architecture-specific issues, and improve turn-around time on issues. Thanks!
Rendered