Add OMIT_PR_CONTAINER_VERSION_UPDATE variable, invert AUTO_MERGE_WORKBENCH_VERSION_UPDATE to default false - #14
Merged
Merged
Conversation
…BENCH_VERSION_UPDATE to default false
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR works with carpentries/actions@2a66f91 to add a new repo env var option, OMIT_PR_CONTAINER_VERSION_UPDATE. When set to
trueon a repo (default is unset orfalse), no PR will be raised when a new workbench-docker version is detected, thus preserving forked histories.Secondly, AUTO_MERGE_WORKBENCH_VERSION_UPDATE is now default
false, previouslytrue. This means when a new workbench-docker version is available (and OMIT_PR_CONTAINER_VERSION_UPDATE is default orfalse) then a PR is raised but not automatically merged. Users will now have to merge these PRs, as with other PRs raised by these workflows.