-
Then, I have a separate "Release" workflow, which is triggered manually using "workflow_dispatch" on the main branch. This workflow fetches the previously built Docker image. (using the branch name as the tag) and runs Semantic Release which creates a GitHub release, based on the commit messages and pushes a new image with the final tag to GCR.
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
I am thinking I would have to create a GitHub release manually and then have a workflow listening on the "Release created" event, which would pull the image with the correct commit sha, tag it with the proper version and push it. Or using something like Release Drafter with a PR-based Git flow.
-
docs
Packagr is a series of small, language-agnostic, dependency-free, composable tools that let you package and release artifacts and libraries written in any language. (by PackagrIO)
Curious if something like https://github.com/PackagrIO/docs would work for your flow.
-
CapsuleCD
Discontinued Continuous Delivery for automating package releases (npm, cookbooks, gems, pip, jars, etc)
Packagr is based off of one of my earlier tools https://github.com/AnalogJ/capsulecd which did this whole flow end to end automatically, but was pretty opinionated, and inflexible. Packagr is setup as a series of small composable tools, which you can integrate with your existing build/test tools & scrips