Before I push something, I perform these steps: • Execute the ./build.sh script to see that I can build a working jar (that I also use locally). • Execute poly test :all which will run all the tests from the poly project. • Execute the https://github.com/polyfy/polylith/blob/master/scripts/create-example.sh script. What it does is described in the script itself, but in short it’s used to produce files that make my life easier and to verify that the compiled poly command works as expected. This step sometimes involves manual work, e.g. when the output from any command has changed. To deploy we perform these steps: • Update the code and documentation to use the latest release in a few places. • Update the sha in the Add other Polylith artifacts as a dependencysection to use the latest sha. • Once these changes are made to the master branch, we create a tag and push it to the master branch, e.g. v0.2.13-alpha. • Once the CircleCI finishes the deployment, it will be deployed to Clojars and GitHub automatically. • Finally we update the version of the https://github.com/polyfy/homebrew-polylith packages and push those changes. I think that was all. As you can se, there are a few manual steps involved today.