When debugging issues that only show up in the Container Image CI (for example due to being ARM platform specific), it would often be useful to quickly iterate CI runs outside a pull-request, by changing the workflow to run on a personal branch.
However in the current version of the action this leads to errors like this.
This is likely due to this setting:
|
push: ${{ github.event_name != 'pull_request' }} |
It would be nice if there was a way to disable this behavior with an override in the downstream workflow (like our container-image also supporting a push flag, same as docker/build-and-publish), or if it checked for master/main/support branches in addition to being on a pull-request. The first option would be my preferred solution.
My current workaround is copying the workflow locally and changing that line to push: false, which is hardly ideal.
When debugging issues that only show up in the Container Image CI (for example due to being ARM platform specific), it would often be useful to quickly iterate CI runs outside a pull-request, by changing the workflow to run on a personal branch.
However in the current version of the action this leads to errors like this.
This is likely due to this setting:
github-actions/.github/workflows/container-image.yml
Line 167 in 30473c8
It would be nice if there was a way to disable this behavior with an override in the downstream workflow (like our
container-imagealso supporting a push flag, same asdocker/build-and-publish), or if it checked for master/main/support branches in addition to being on a pull-request. The first option would be my preferred solution.My current workaround is copying the workflow locally and changing that line to
push: false, which is hardly ideal.