-
Notifications
You must be signed in to change notification settings - Fork 161
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
Safe-settings for peribolos investigation #3618
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Comments
Creating this as an issue for us to keep our eyes on if the project ever matures. |
This issue is stale because it has been open for 90 days with no |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Feb 14, 2023
/lifecycle frozen |
knative-prow
bot
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Mar 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/github/safe-settings is the ideal type of git-ops configuration that would be desirable https://github.com/github/safe-settings#the-settings-file. It would also be able to handle branch protection and enable repo owners to configure access to their repos by giving access to the repo subdir of the
admin
repo.Setup involved https://github.com/github/safe-settings/blob/main-enterprise/docs/deploy.md deploying the app by:
admin
repo and provide a settings file.The org creation and management works much quicker than with peribolos. However, teams didn't seem to be implemented at the time of evaluation github/safe-settings#251 and thus does not bring us to feature parity with peribolos. Another observation is that the project seems to be lead and maintained by one person and there are quite a few things that are lacking for a more robust mature project, such as a roadmap etc.
The text was updated successfully, but these errors were encountered: