You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the untriaged workflow to add the untriaged label to all new issues, as described in #133
This is a good mechanism to ensure each repository has the right processes in place to routinely triage issues, where the label is manually removed. It also supports accountability, because we can simply check for untriaged issues that have had that label for some time.
But this does add unnecessary overhead to maintainers, who often create the majority of all issues in a repository, particularly when breaking down large epics or initiatives into subtasks. This can lean to temporary spikes in the untriaged metrics until the newly created issues are manually cleaned up.
What solution would you like?
By definition, a triaged issue is one which maintainers have deemed valid. So the untriaged workflow should simply skip any issues created by maintainers. I'm not sure of the best programmatic way to access the maintainer list from within the workflow, but suspect that the newly baselined CODEOWNERS files will help.
It would be amazing to turn the untriaged workflow into a proper GitHub app similar to DCO with features such as this one, so we don't have to configure a manual workflow in every repo.
Is your feature request related to a problem?
We use the untriaged workflow to add the
untriaged
label to all new issues, as described in #133This is a good mechanism to ensure each repository has the right processes in place to routinely triage issues, where the label is manually removed. It also supports accountability, because we can simply check for untriaged issues that have had that label for some time.
But this does add unnecessary overhead to maintainers, who often create the majority of all issues in a repository, particularly when breaking down large epics or initiatives into subtasks. This can lean to temporary spikes in the untriaged metrics until the newly created issues are manually cleaned up.
What solution would you like?
By definition, a triaged issue is one which maintainers have deemed valid. So the untriaged workflow should simply skip any issues created by maintainers. I'm not sure of the best programmatic way to access the maintainer list from within the workflow, but suspect that the newly baselined
CODEOWNERS
files will help.What alternatives have you considered?
None so far.
Do you have any additional context?
Related to #102
The text was updated successfully, but these errors were encountered: