Workflow to automate release process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 150
- Forks
- 23
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 2
Description
In the near future, we could probably automate our releases, at least in part, by combining some & ideally all of the steps from our release checklist into one, or perhaps a series of, Actions workflows.
Some steps are clearly trivial to automate as they are already commands with some parameters, but others may be difficult.
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 locating the release checklist and any existing GitHub Actions workflows, then map which checklist steps are already commands and which need further design. Done means the agreed release steps run through one or more Actions workflows with the remaining manual work clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100