-
Notifications
You must be signed in to change notification settings - Fork 876
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEA] GitHub Issue Infrastructure Update #13504
Comments
Oh right when I do these PR's I'll also axe:
Projects now have a built-in workflow to add to project, and all classic projects have been closed. |
Hello @jarmak-nv, I noticed this issue while triaging cudf 😂. My process has been to check the At the same time, I like the idea of giving a special label to externally-filed issues. |
I think I've come around to the feedback on #13542 and will drop the issue template part of it (because there's no ETA on the length fix) and update the GHA to use This way we can have a slack channel that alerts us to any activity on an issue/PR that's labeled |
Done - assuming all are happy with the GHA, all it needs is someone with |
@jarmak-nv @GregoryKimball could you comment on whether this issue is still actionable? |
Good question! Been very away from this for a bit, but I'd be happy to contribute a PR to label external issues if that's something that's still valuable. The replacing |
@GregoryKimball WDYT? Do you like the idea of an external label? |
Describe the solution you'd like
I'd like to (in 2 separate PRs)
1. Replace .md issue templates with .yml formsWith these templates I'd remove the https://github.com/rapidsai/cudf/labels/%3F%20-%20Needs%20Triage label from always being on new issuesDescribe alternatives you've considered
We could also do triage rotations with the GHA but I prefer the auto-labeling and leveraging the label to track as needed.
Additional context
We do this in Morpheus - references:
Looking to solicit feedback prior to making any changes. If feedback is all 🟢 then I'll PR these changes in ASAP and we can work through the specific implementations in the PR review.
The text was updated successfully, but these errors were encountered: