Rework setting image tags to support PRs better #161
Merged
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.
Changes introduced with this PR
This PR reworks the reusable workflow which builds plugin container images. It combines into one all the steps which handle different cases of generating container image tags depending on the CI trigger. And, if the trigger is a Pull Request, it uses the name of the PR branch instead of the name of the GitHub "ref" (which is usually something generic, like
17/merge
). And, it picks a few bits of lint.So, the tags will now be one of the following:
release
andlatest
[this is unchanged]main
branch:main_latest
[this is unchanged]<PR_branch_name>_<last_commit_hash>
[this is new]<tag-name_or_branch-ref>_<commit_hash>
[this is unchanged]This PR was tested using arcalot/arcaflow-plugin-rtla#5 for PR builds and for tag builds, and it will use arcalot/arcaflow-plugin-rtla#4 for testing
main
builds (i.e., once this PR is merged, then that one can be merged, and then this one will get tested 🙂).By contributing to this repository, I agree to the contribution guidelines.