-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Invite current stable prometheus chart maintainers as collaborators with write access #12
Comments
👋 |
Invited all current maintainers as collaborators to this repo, and also pinged everyone in Slack ✅ |
Will close this issue for now since tasks are done ✅ but we can still comment here in the meantime if there is overwhelming concern about implementation and re-open if needed ⏳ |
I believe we should keep the I do think though that we should all have owners permissions regarding the repo. This shouldn't take away from the actual permission to push commits/approve PRs for the different charts. |
@Xtigyro after slack chat, I understand what you mean. OK so yes, keeping |
…-refactor-json-schema Updates to image values format and JSON Schema for Rekor
* Add externalTrafficPolicy for LB service * Fix PR Comments
* Add externalTrafficPolicy for LB service * Fix PR Comments
[kube-prometheus-stack] change rules sync source to kse-prometheus
stable
- [ ] 3. cleanup: remove the prowEdit: will be done as part of Prep initial charts indexing #14 so the initial helm index will be cleanOWNERS
files📊 Maintainers poll
Do we want to keep this level of granularity, or would it be better to give all collaborators write access to all charts in this repo? Let's discuss in comments below…
The text was updated successfully, but these errors were encountered: