Open jarmak-nv opened 1 year ago
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 ? - Needs Triage
flags every week or two and then assign labels, milestones and project status at that time. If we stopped using the ? - Needs Triage
label.. I would miss issues like this!
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 external
as the label.
This way we can have a slack channel that alerts us to any activity on an issue/PR that's labeled external
and we don't interrupt existing processes.
Done - assuming all are happy with the GHA, all it needs is someone with write
+ access to the cuDF repo to create an external
label.
@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 .md
s with .yml
s has officially been shelved though
@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 forms~
Describe 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.