Please refer to our FAQ and look at our known issues before opening a bug report.
Describe the bug
When creating a new release, the procedure consists of running pypi_publish and then docker. pypi_publish checks out the correctly tagged branch, however docker checks out the main branch. This is because running a workflow after the success of another workflow checks out the default branch (main).
Expected behavior
The docker workflow should build the docker image based on the tagged branch used in pypi_publish, so it should check out refs/tags/vX.Y.Z instead of refs/remotes/origin/main.
To Reproduce
Make a new release and watch it happen live.
Please refer to our FAQ and look at our known issues before opening a bug report.
Describe the bug
When creating a new release, the procedure consists of running
pypi_publishand thendocker.pypi_publishchecks out the correctly tagged branch, howeverdockerchecks out themainbranch. This is because running a workflow after thesuccessof another workflow checks out the default branch (main).Expected behavior
The
dockerworkflow should build the docker image based on the tagged branch used inpypi_publish, so it should check outrefs/tags/vX.Y.Zinstead ofrefs/remotes/origin/main.To Reproduce
Make a new release and watch it happen live.