pytest-dev / pytest-dev/pytest
[maintenance] Have a GH CLI extension as an entry point for release automation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
What's the problem this feature will solve?
I noticed that some of the release automation activities involve running bare GH CLI commands with arguments that have to match pre-release activities. This might be error-prone. Instead, the process could benefit from having simpler commands that mostly just point to things like a PR number.
Describe the solution you'd like
Have a GH CLI extension so that it's possible to use it as an entry point instead of more complex subcommands. A-la gh pytest-infra release --version=9.0.1.
Additional context
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 by inspecting the existing release automation activities that run bare GH CLI commands and compare their pre-release arguments. Read the linked GitHub CLI extension guidance and evaluate the proposed gh pytest-infra release --version=9.0.1 entry point. Done means the release process has simpler extension commands that accept the intended release inputs without error-prone command matching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- cli, release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100