I still had to run the ./deploy.sh script after committing changes. Not anymore - I’m calling this script in a github action being run after a push to master! Some refactoring was required - I moved the command related to pushing the generating site to a separate script, and this script is called from github actions. UPDATE: this did not work at all! I resorted to trying out a lot of push Github Actions but none worked....
Spring boot offers out-of-the-box support for git-commit-id-plugin, where you can bind git properties to Spring variables. However heroku cannot work with this. After some reading up, it appears that the hidden .gitsubfolder is not pushed to heroku. Since during build time the git.propertiesfile is generated and saved in the target folder, the git-commit-id-plugin will fail as there is no .gitsubfolder. Then I stumbled on the heroku-maven-plugin. This plugin allows to build your project locally and then push the artifact to heroku - and that’s what I need....
Deploying to github pages is not as easy as I thought. I tried several things for building a Github Action workflow, however this is only meant for actions related to the repository in question. In the end, I follow the approach as mentioned on the Hugo website with a local script. I have pimped it by fetching the latest commit message and the use this message for committing the changes in the generated site....