tests: follow the Action example into docs/usage.md - #35
Merged
Merged
Conversation
The example the release tooling rewrites moved to the usage guide when the README became a front page, and the tooling moved with it; its test kept building a tree with the example in README.md, so every case failed on a missing file.
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.
The example the release tooling rewrites moved to the usage guide when the
README became a front page (#33), and
infra/prepare-action-releasemovedwith it. Its test kept building a tree with the example in
README.md, soevery case in
test_action_release.pynow fails on a missing file.Point the fixture at
docs/usage.md, and snapshot files withrglobsincethe tree now has a directory in it.