We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current state of the reset_test_repo.yml only seems to take care of the code, branching and repo variables/secrets
Branch protection rules are not yet part of it and need to be added.
Most likely the gh cli tool also is capable of setting up branch protection rules to ensure it behaves just as an Ayon-Addon-Repo would.
This includes
main
develop
None
No response
The text was updated successfully, but these errors were encountered:
This is done for the most part but needs to be checked against one of the addon repos
Sorry, something went wrong.
This is still the case due to the intitial rulesets not workign anymore
philnewm
No branches or pull requests
Is there an existing issue for this?
Please describe the enhancement you have in mind and explain what the current shortcomings are?
The current state of the reset_test_repo.yml only seems to take care of the code, branching and repo variables/secrets
Branch protection rules are not yet part of it and need to be added.
How would you imagine the implementation of the enhancement?
Most likely the gh cli tool also is capable of setting up branch protection rules to ensure it behaves just as an Ayon-Addon-Repo would.
This includes
main
branch should be protected accordinglydevelop
branch should be protected accordinglyAre there any labels you wish to add?
Describe alternatives you've considered:
None
Additional context:
No response
The text was updated successfully, but these errors were encountered: