Release automation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Description
For the time being, the automatic creation of a new docker image version is triggered by the creation of a new Github release, which is a manual process, indeed one must do the following:
- create and push a new tag
- manually create and publish a release based on the tag
It would be nice to have an automation in place that triggers the Github release automatically, upon a user action (either a push of the tag or the manual run of a GitHub workflow, as in KIC)
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
Review the repository's existing GitHub workflows and the KIC release.yaml example linked in the issue. Compare tag-push and manually dispatched workflow triggers, then define the workflow behavior needed to create a GitHub release and trigger the Docker image version automatically. Done means the manual release steps are replaced by a tested automation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100