Skip to content
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

Testing repo reset not on par with actual addons repos #16

Open
2 tasks done
philnewm opened this issue Sep 17, 2024 · 2 comments
Open
2 tasks done

Testing repo reset not on par with actual addons repos #16

philnewm opened this issue Sep 17, 2024 · 2 comments
Assignees

Comments

@philnewm
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues.

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

  • branch protection rules
  • Adding bypass users/groups
  • enforcing certainr equirements for PRs and/or pushes
  • main branch should be protected accordingly
  • develop branch should be protected accordingly

Are there any labels you wish to add?

  • I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

None

Additional context:

No response

@philnewm philnewm added the enhancement Extend an existing feature label Sep 17, 2024
@philnewm
Copy link
Collaborator Author

This is done for the most part but needs to be checked against one of the addon repos

@mkolar mkolar removed the enhancement Extend an existing feature label Oct 30, 2024
@philnewm
Copy link
Collaborator Author

This is still the case due to the intitial rulesets not workign anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants