ansible-docs-build-html - first tests, rename move-build to copy-build
#18
Conversation
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
briantist
changed the title
ansible-docs-build-html - first tests, rename move-build to copy-build
briantist
added a commit
that referenced
this pull request
Jan 15, 2022
felixfontein
approved these changes
Jan 16, 2022
Collaborator
|
@briantist thanks for adding tests! |
felixfontein
pushed a commit
that referenced
this pull request
Jan 16, 2022
* add tests for build-init action * add .test path from #18 * add a requirements.txt * flesh out the init tests * fix defaulted * fix defaults again * round 3
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.
Here's a first pass at a workflow that runs tests for an action.
This one aims to test the
ansible-docs-build-htmlaction. I kept it simple so I could get it uploaded first.IIRC, even though this branch is in the main repository, I believe it still will not run in this PR until it lands inI was wrong! I guess that only applies to new workflows from forks, andmainonce (after that, changes to it should run in PRs).pull_request_targettriggers in all cases.EDIT: writing tests for the
move-buildparameter made me realize I was not moving the files, but rather copying them! Instead of changing the behavior, I've changed the name of the parameter tocopy-buildand have updated its usage, references, and descriptions, and the tests confirm its behavior.