open-telemetry / open-telemetry/opentelemetry-python
Use matching branch names for Prs created from prepare release workflow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem?
For PRs that are created automatically as part of the prepare-release-branch.yml workflow, we use specific release branch names. As part of making the tests pass, maintainers must manually update the SHA. Investigate the possibility of using specific branch names so we can change the SHAs programatically as part of the prepare-release workflow instead of having to change it manually. One PR will most likely fail due to the corresponding branch in the other repo might not be created yet, but a simple rerun should most likely make builds pass.
Describe the solution you'd like
.
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
None
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
Start with .github/workflows/prepare-release-branch.yml around line 70 and inspect PR 4246 for the current automatically created release branches and manual SHA updates. Trace how the workflow names branches and updates SHAs across the related repository. Done means the workflow can use matching branch names and update the SHAs programmatically, with reruns handling a branch that was not initially available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100