.github: clean up logic in docker build workflow to cleanly separate … #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…prs and merges
Overview
This workflow has been buggy for a while due to the splitting of the two build steps and the differences in the teams work flow. The issue from https://github.com/celestiaorg/devops/issues/527 came down to the same commit being present on the PR as well as on main, thus causing the new docker images not to be built. This can happen based on how the team creates branches, forks, PRs, etc.
The workflow now runs with the following logic:
This PR is a replacement of #76