Repository settings in addition to what's documented already at https://github.com/open-telemetry/community/blob/main/docs/how-to-configure-new-repository.md.
- Allow squash merging > Default to pull request title
-
Fork pull request workflows from outside collaborators: "Require approval for first-time contributors who are new to GitHub"
(To reduce friction for new contributors, as the default is "Require approval for first-time contributors")
The order of branch protection rules
can be important.
The branch protection rules below should be added before the **/** branch protection rule
(this may require deleting the **/** rule and recreating it at the end).
-
Require branches to be up to date before merging: UNCHECKED
(PR jobs take too long, and leaving this unchecked has not been a significant problem)
-
Status checks that are required:
- EasyCLA
- required-status-check
Same settings as above for main, except:
-
Restrict pushes that create matching branches: UNCHECKED
(So that opentelemetrybot can create release branches)
-
Require status checks to pass before merging: UNCHECKED
(So that renovate PRs can be rebased)
-
Restrict who can push to matching branches: UNCHECKED
(So that bots can create PR branches in this repository)
-
Allow force pushes > Everyone
(So that renovate PRs can be rebased)
-
Allow deletions: CHECKED
(So that bot PR branches can be deleted)
-
Everything UNCHECKED
(This branch is currently only used for directly pushing benchmarking results from the overhead benchmark job)
GPG_PASSWORD- stored in OpenTelemetry-Java 1PasswordGPG_PRIVATE_KEY- stored in OpenTelemetry-Java 1PasswordDEVELOCITY_ACCESS_KEY- owned by @jack-berg- Generated at https://ge.opentelemetry.io > My settings > Access keys
- format of env var is
ge.opentelemetry.io=<access key>, see docs
SONATYPE_KEY- owned by @jack-bergSONATYPE_USER- owned by @jack-berg