Bjørn Erik Pedersen

>Could it be the paths filtering? According to the docs and my tests (https://github.com/bep/githubactionstest/actions); no. But it's a little hard to test this ... I don't want to create dummy...

OK, I just pushed this tag to master: https://github.com/gohugoio/hugo/releases/tag/testbuild1 Which did not trigger a package build, which I guess is great news as it means we can test it without...

OK, so reducing it to this seems to work: ``` on: push: tags: - "*" ``` Mysterious ... Oh, well. I can add a `workflow_dispatch` so we can start it...

OK, the release I just did, sadly did not trigger a build. OK, I don't understand this and I currently don't have more time to spare on this.

This smells like a GitHub bug, but my current theory and workaround is: * We create the release tag on a release branch. * Then we merge the release branch...

>[ci skip], so the Docker workflow was skipped. OK, that may be it, but that `[ci skip]` is there for a reason (to stop triggering another release build). There may...

I tried to fix this, but had to revert, see 73d32e7737082118a48adb8db3ff1ed7407f4d3f If someone knows (no guessing, please) how to set this up in CircleCI, a PR is welcome...

I have done some further experiments (no luck) here: https://github.com/bep/circlecitest I'm putting this work on pause myself, but I welcome tips/prs in the above repo. The goal is to control...

OK, so @razonyang has come up with a circle CI setup that gets us around this issue; I will set it up in Hugo early the coming week.

Unfortunately my new and promising attempt to update the Circleci build for this (repeatedly) failed with a cryptic error: