Repository navigation
test: expect pre-commit hook install line for frogtab clones - #219
Merged
Merged
Conversation
The repo dwilding/frogtab added '.pre-commit-config.yaml' on 2026-10-31 (release commit 066a2821). Since then, gimmegit prints 'Installing pre-commit hook' after cloning frogtab, but four functional tests still assert stdout without that line, so they fail. Update the expected stdout in test_outer.py and test_outer_clone.py to include the line. This fixes the functional-limited CI failures seen on PR #218 and other branches. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dwilding
changed the title
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
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 fixes the functional tests that clone dwilding/frogtab. Now that the repo includes pre-commit config, we need to account for the pre-commit message that gimmegit outputs.