open-telemetry / open-telemetry/community
GitHub feature wishlist
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 314
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Description
Tracking the GitHub missing features that are directly impacting OpenTelemetry.
- Support "Restrict who can push to matching branches" in Rulesets
- We use this extensively in classic branch protections and this missing feature is blocking us from moving to the modern rulesets.
- Split out repo deletion permission in fine-grained tokens
- We use a classic token for GitHub administration via Infrastructure as Code, because classic tokens have a separate permission for repo deletion, and we really really don't want to accidentally delete all our repos via IaC.
- This missing feature is blocking us from using GitHub App token for IaC workflows.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the two linked GitHub discussions and the issue's description of OpenTelemetry's Infrastructure as Code needs. No repository file or test is identified; completion would require confirming that the requested GitHub permissions and ruleset capability are available before updating this tracking issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100