-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Use shared workflow action on issues #12382
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same thought here on not getting too confused with all the issues related workflows.
With the addition of this workflow, we will have 3 issue workflows. There is a general one that assigns to project and another one that is community specific.
Would it make sense to consolidate all these for now? I'm not too opinionated about the eventual form. I mainly want to avoid confusion if these are too scattered around and want us to treat this intentionally.
Once this gets merged to this shared code is running, I can consolidate the community tag that @harshithmullapudi added so we don't miss any of those into the workflow-actions code. The platform project routing workflow can be deleted when we verify with @pmossman and @benmoriceau that they are no longer using it. |
Combining or deleting those are definitely next steps @davinchia |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for following up on the workflows. I'll leave it to you then!
* Use shared workflow action on issues * Rename to token * Also on unlabeled
Tags issues to route to correct teams.