Add build workflow - #7
Merged
Merged
Conversation
Adds dry_run and path inputs so CI can run the action against a throwaway copier project without pushing a branch or opening a pull request. The fixture lives under RUNNER_TEMP because the action checks out the repo itself, which would clean anything staged in the workspace. Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
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.
Builds a throwaway copier template and a project generated from it, advances
the template, then runs
./updateagainst that project and checks the updatelanded.
Two inputs were needed to make the action testable at all:
dry_run(defaultfalse) stops before the branch push andgh pr create.path(default.) points the copier steps at a project directory. Thefixture has to live under
RUNNER_TEMP, because the action checks out thisrepo as its first step and that cleans anything staged in the workspace.
Both default to current behaviour, so existing consumers are unaffected.