open-telemetry / open-telemetry/community
Github cache limits going to be enforced in November
Open
Nobody has claimed this yet.
area/github
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 314
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Description
I got the below email about my github cache usage. It doesn't tell me which repository caused the email but I suspect it is an OTel one since I don't often use personal repositories and none of them show any recent activity.
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
No file, test, or entry point is named. Start by reviewing the email screenshot and the repository's GitHub Actions configuration to identify whether an OpenTelemetry repository caused the reported cache usage. The issue is complete only when the source of the usage and the required remediation are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100