Forced SHA update workflow #5560
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
github_actions
vepatel
approved these changes
May 16, 2024
j1m-ryan
approved these changes
May 16, 2024
jjngx
approved these changes
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Adds a workflow which can force the latest SHAs for images pinned in
build/Dockerfileandtests/Dockerfile. This opens a PR against the branch that it targets, so should work formainorrelease-*branches. Also supports excluding images that match a given pattern.Sample PR (Note: branch name is incorrect as it was triggered from a push, branch name will normally be
chore/image-update-<source branch>-<dockerfiles hash>)Checklist
Before creating a PR, run through this checklist and mark each as complete.