Automate Releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Since we already insist on having people work on dev branches & master branches only incorporating stable code, we could also produce a way of making automated releases too:
https://github.com/semantic-release/semantic-release
This would only require:
- Setting the
masterbranch protected for everyone, except for PRs coming fromdev - Forcing everyone to NEVER merge to
masterexcept for releases that have been tested ondev(which we anyways do)
Could then configure the method above to make a release whenever coming from master and something has been changed. If people then also use the CHANGELOG.md, it would automatically do proper and nice releases :-)
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 reviewing the semantic-release proposal and the repository's dev and master branch workflow, including CHANGELOG.md. Done means releases are triggered for changed, tested code reaching master, with the stated branch protection and merge rules in place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100