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
The taxonomy triage team uses labels on pull requests for tracking and notification purposes. It would be helpful to users to add a few of these labels to the contribution dashboard. Documentation around labels can be found here triaging-contributions.md - instructlab/taxonomy (it is very out of date, i’ll get that updated). IMO we should include “triage-requested-changes”, “e2e-ready”, and “triage-rejected”. Feedback welcome and encouraged!
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue @juliadenham . Appreciate it. It would be great if you can update the issue, whenever the labels related document is updated, so we can use the latest and greatest.
After discussion with triage team, following is the list of labels that we should translate to either status or action for the user.
cmb-running (status)
cumminity-build-ready (status)
knowledge (status)
legal-hold (status)
precheck-generate-ready (status)
question (action)
ready-to-merge (status)
sdg-unsuccessful (status)
skill (status)
stale (status and possible associated action)
topic-failure (action)
triage-needed (status)
traige-rejected (status)
traiage-request-changes (action)
status labels are just the progress notifications. Action labels are something that requires users attention and might require update to their contribution.
@Misjohns I think if you can help us designing the mock-up that shows the status as well as actions for each contribution, i think this story can get to ready state.
The taxonomy triage team uses labels on pull requests for tracking and notification purposes. It would be helpful to users to add a few of these labels to the contribution dashboard. Documentation around labels can be found here triaging-contributions.md - instructlab/taxonomy (it is very out of date, i’ll get that updated). IMO we should include “triage-requested-changes”, “e2e-ready”, and “triage-rejected”. Feedback welcome and encouraged!
The text was updated successfully, but these errors were encountered: