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
While we have a triaging workflow for feature requests in addition to labeling (i.e. 'community contribution' and the Enhancement Project Board), our contributors don't get a clear look into the triage process. The goal of this issue is to utilize a triage bot to increase transparency into our process within Github issues, automate wherever possible, and find a better way to kick off community contribution work.
Info provided by Taylor:
We'll need to make a workflow to house the logic for when and how to post the messages to issues.
There aren't triggers (yet?) for events that happen within the new github projects, like moving pipelines. The existing project trigger only works for classic projects 😞
We won't be able to use hramos/label-actions@v1 but we should be able to get the same result using if expressions on different jobs or steps in the workflow and use actions/github-script@v6 to add the comment
aubrey-oneal
changed the title
Update Github contributor triaging (add labels, github bot messages)
Create a Github Triage Bot
Jul 19, 2023
aubrey-oneal
changed the title
Create a Github Triage Bot
Create initial designs for a Github Triage Bot
Jul 24, 2023
While we have a triaging workflow for feature requests in addition to labeling (i.e. 'community contribution' and the Enhancement Project Board), our contributors don't get a clear look into the triage process. The goal of this issue is to utilize a triage bot to increase transparency into our process within Github issues, automate wherever possible, and find a better way to kick off community contribution work.
The text was updated successfully, but these errors were encountered: