Allow running `build-release.yml` against a branch
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 48
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 4
Description
Currently, .github/workflows/build-release.yml takes a tag number:
Which can be used as the input when triggering a run:
https://github.com/python/release-tools/actions/workflows/build-release.yml
It would be useful if we could also give a branch name, so for example we can trigger a run against upstream main or 3.14, so we can verify the latest state will build.
This will also help with PRs like https://github.com/python/release-tools/pull/284 where we specify which arguments to run against the Android test runner, and the test runner is in the upstream repo.
We'll need to take care of v prefix that is currently prepended in some places.
Contributor guide
No contributing guide indexed for this repository
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/build-release.yml at the input definition around lines 35-37, then trace where that value is used. Support both branch names and tag numbers while preserving the existing v-prefix behavior, and verify that the workflow can build against upstream main or 3.14 as well as existing tag inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100