Skip to content

HIP 0005 - Structured Labels - #1978

Open
yoshuawuyts wants to merge 5 commits into
mainfrom
labels-hip
Open

yoshuawuyts wants to merge 5 commits into
mainfrom
labels-hip

Conversation

@yoshuawuyts

@yoshuawuyts yoshuawuyts commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

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

Signed-off-by: Yosh <github@yosh.is>
Copilot AI balanced review requested due to automatic review settings October 23, 2026 10:49
@yoshuawuyts yoshuawuyts added kind/enhancement For PRs adding features, improving functionality, docs, tests, etc. area/infrastructure Concerns infrastructure rather than core functionality labels Oct 23, 2026

This comment was marked as resolved.

yoshuawuyts and others added 3 commits October 23, 2026 12:56
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>
Signed-off-by: Yosh <github@yosh.is>
@yoshuawuyts yoshuawuyts added the meeting-nominated Item nominated for the next triage meeting label Oct 23, 2026
andreiltd
andreiltd previously approved these changes Oct 26, 2026
| `area/testing` | `A-testing` |
| `github_actions` | `A-ci` |
| `good first issue` | `E-easy` |
| `Guest-COW` | `F-guest-cow` |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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

@yoshuawuyts yoshuawuyts Oct 29, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

There is tooling in github now that lets us set the same labels across the org. We should use that

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good point!

Comment thread proposals/0005-structured-labels/README.md Outdated
Comment thread proposals/0005-structured-labels/README.md

@jsturtevant jsturtevant left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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

Comment thread proposals/0005-structured-labels/README.md
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Yosh <github@yosh.is>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/infrastructure Concerns infrastructure rather than core functionality kind/enhancement For PRs adding features, improving functionality, docs, tests, etc. meeting-nominated Item nominated for the next triage meeting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants