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

REQUEST: Repository maintenance on opentelemetry-operator #1597

Closed
jaronoff97 opened this issue Jul 14, 2023 · 4 comments
Closed

REQUEST: Repository maintenance on opentelemetry-operator #1597

jaronoff97 opened this issue Jul 14, 2023 · 4 comments
Labels
area/repo-maintenance Maintenance of repos in the open-telemetry org

Comments

@jaronoff97
Copy link

jaronoff97 commented Jul 14, 2023

Affected Repository

https://github.com/open-telemetry/opentelemetry-operator

Requested changes

override default branch protections for opentelemetrybot/**/**, same as:

#### Branch protection rule: `dependabot/**/**`

Purpose

Our auto-updating java agent working is failing (open-telemetry/opentelemetry-operator#1922)

Expected Duration

Permanently

Repository Maintainers

  • @open-telemetry/operator-maintainers
@jack-berg
Copy link
Member

I'm starting work on this.

@jack-berg
Copy link
Member

jack-berg commented Jul 18, 2023

I've updated the branch protection rules.

@jaronoff97 can you add a .github/repository-settings.md file documenting these changes? Example here.

@trask
Copy link
Member

trask commented Jul 19, 2023

can you add a .github/repository-settings.md file documenting these changes? Example here.

currently documenting these changes is only asked of maintainers who have admin privilege on their repository (so they can make the changes themselves without opening a request here):

If requested, `foo-maintainers` will be granted `Admin` permissions, and in return
they must document any changes they make to the repository settings in a file named
`.github/repository-settings.md` in their repository (other than temporarily
disabling "Do not allow bypassing the above settings", see branch protection rules
below).

we can definitely expand this, but I'd suggest seeing where #1596 goes first

@jack-berg
Copy link
Member

Sounds good. Seems like its pretty roundabout to find the provenance of a repository setting change with the current setup. I would love an infrastructure as code solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/repo-maintenance Maintenance of repos in the open-telemetry org
Projects
None yet
Development

No branches or pull requests

3 participants