-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Improve POSIX shell compatibility in pre-push hook #4053
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
Conversation
PeterDaveHello
left a comment
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.
Shouldn't I be the git commit author then? The bot can be committer.
Hello Roo Team! We received this contribution on the Kilo side and thought it might be useful to you! This change improves consistency in the pre-push script and improves compatibility with different types of shells. Original pull request: Kilo-Org/kilocode#515
1d5ff8e to
1201ed5
Compare
|
@PeterDaveHello you're right, I adjusted the author field. Sorry for the inconvenience. |
|
LGTM! Since using = instead of == is the POSIX-compliant way for string comparison in single bracket tests, I think we should have this as well. Thanks for the fix! |
Hello Roo Team! We received this contribution on the Kilo side (thanks @PeterDaveHello!) and thought it might be useful to you!
Description
This change improves consistency in the pre-push script and improves compatibility with different types of shells.
Original pull request: Kilo-Org/kilocode#515
Type of Change
srcor test files.Important
Fix string comparison operator in
.husky/pre-pushfor better POSIX shell compatibility.==to=in.husky/pre-pushto improve POSIX shell compatibility.This description was created by
for 1d5ff8e21c06b92b2e2000715deaf8fc4c941bdf. You can customize this summary. It will automatically update as commits are pushed.