openwisp / openwisp/openwisp-utils
[feature] Release workflow: automatically publish tag and release
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 93
- Forks
- 104
- Avg merge
- 14h 10m
- Merged PRs (30d)
- 22
Description
Follow up of #496.
We could add a github action which detects the commit message generated by the releaser tool and automatically push a git tag and publish a release. This would help further automating the release workflow, which now needs the review and approval of a maintainer, while another maintainer needs to keep the release flow open waiting for the PR to get merged, which may not happen while the maintainer is still around.
We also need to modify the releaser tool to play well with this case, I guess it should be able to go straight to the git tag part and release part. Not sure what we can do with the signature, I guess I can create a new signature and make it available as an organization secret.
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 #496 and the existing release workflow and releaser tool; no file paths or tests are named. Define how the workflow detects the releaser-generated commit, then verify the intended outcome: a git tag and published release without maintainer intervention, including a decided approach to the signing secret.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100