-
Notifications
You must be signed in to change notification settings - Fork 0
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
New PR should have automatically assigned Ynteam active
project
#22
Comments
Thats good stuff 👍 on:
pull_request:
types:
- opened
paths:
- '.github/workflows/**'
- '.github/CODEOWNERS'
- 'package*.json' The bigger challenge here is to implement a standardized approach for all intended repositories. So I see too options here
|
Good questions. Let's first assume that it is something we want to be automated - and I am assuming there is no reason we do not, right @dee-ynput ? I believe this should be organization wide workflow and only purpose is to simply attach |
Ynteam planning
projectYnteam active
project
Definitelly and org wide workflow |
I tested this now with ayon-maya and it does already work for all newly created prs @jakubjezek001 should the status be set to anything or is "No status" fine as long as the PR is assigned to the project? |
This is now implemented and pushed to all addon repos bb9327 |
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Currrently every new PR has to have manually assigned
Ynteam active
projectHow would you imagine the implementation of the feature?
It would be awesome if avery new PR would be automatically have assigned Ynteam Planning project.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: