Stash before running prepush hook tests #368
Merged
Conversation
This file contains 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
tom-coward
approved these changes
Feb 13, 2025
tom-coward
added a commit
that referenced
this pull request
Feb 18, 2025
This reverts commit a36419c.
tom-coward
added a commit
that referenced
this pull request
Feb 18, 2025
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.
📺 What
Runs
git stash push -qubefore the prepush hook tests and runsgit stash pop -qafter them. This allows for unstaged in development tests to be present without having to pass whilst still verifying what is being pushed. Prevents potentially running--no-verifyor similar to just get something pushed.🛠 How
Source Control
✅ Testing
Tested by changing a test to fail (
expect(true).toBe(false)) and not staging it whilst pushing this change - test was not included in index and did not affect prepush hook checks.