-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Bug]: Tempest scripts has Windows-style line endings, which breaks the env
call in the shebang
#826
Comments
I tend to use the following in my
For me, personally, it doesn't seem to cause any issues. I am also on Windows with
As far as I am aware, ** My apologies if I misunderstood anything, it's very early in the morning and I'm running on no sleep :D lol |
Do you mean there are |
@brendt yes exactly! @ericsizemore 's comment about gitattributes might be worth checking out. I can test this out when I'm home later. |
Thanks, and yes please do! Feel free to submit a PR to our |
Great ideas! For what it's worth, a lot of this stuff is what is happening in Laravel as well, so might be a place to look for reference. |
Oh absolutely! I'll check out what Laravel does. Thanks! |
Tempest Version
1.0-alpha4
PHP Version
8.3
Operating System
Windows, Other
Description
Operation System: Windows/WSL2.
PHP version: 8.4.1
Some scripts, e.g. the
tempest
script has issues with Windows-style line endings (\r\n
). By replacing all the Windows-style line endings with Unix-style line endings makes the scripts run as expected.I checked my global Git config and I use
core.autocrlf
, meaning Git will replace all line endings with Windows-style line endings. Maybe we should set this value to false in the tempest repositories to avoid this issue?Steps to Reproduce
Run any tempest command, e.g.
tempest serve
in a WSL2 terminal.The text was updated successfully, but these errors were encountered: