-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redirect input to terminal only when running through terminal #8362
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.27 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @timur27! This fixes the issue and allows VS Code Git: push
commands 🙌✨
Co-authored-by: Timur Karimov <[email protected]>
Fixes #8360
Changes proposed in this Pull Request
This PR adds some checks in the
pre-push
husky hook which help distinguish if the script is being run in the terminal or not.Testing instructions
pre-push
guards are working fine (follow the instructions from Avoid accidental pushes todevelop
andtrunk
#8287)Git: push
from the VS Code command palette and confirm the error described in Husky pre-push script preventsgit push
via VSCode command #8360 isn't there anymorenpm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge