-
Notifications
You must be signed in to change notification settings - Fork 12
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
Create workflow to add primer/behaviors issues to the Primer teams backlog for triage #239
Conversation
|
@lesliecdubs let me make sure these vars/secrets get added while we setup the one for PVC too! I'll leave a message here once it's done 👍 |
@lesliecdubs made sure the variables and secrets are available so should be good to go now! |
Co-authored-by: Josh Black <[email protected]>
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.
Looks like @jonrohan added the necessary variables + secrets, so we should be good to merge this 👍
Confirmed working 🎉 |
Thanks all ✨ |
I noticed recently that issues filed in the
primer/behaviors
repo don't end up in our inbox for triage (e.g. https://github.com/orgs/github/projects/4503), so are likely getting missed.This PR attempts to create an "add to inbox" workflow for this repo so that new and reopened issues will get labelled as
react
andrails
(so we can discuss at the appropriate weekly maintainer syncs) and moved into the Inbox of the Primer teams backlog.Questions:
vars
,steps
, andsecrets
used in this workflow valid? I assumed these values are defined in the specified actions, but would be good to confirm.primer/behaviors
issues?