-
Notifications
You must be signed in to change notification settings - Fork 84
feat: add interpreter detection for various script types #1618
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
@@ -40,6 +40,7 @@ requests = ">=2.32.2,<2.33" | |||
syrupy = "4.6.*" | |||
rust-src = ">=1.86.0,<1.87" | |||
boto3 = "*" | |||
nushell = "==0.104.0" |
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.
I think this can be reverted since you are also requesting nushell
in the build requirements of the recipe.
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.
Nope, github runners for some reason doesnt see it without adding specially to lock file. This could be a bug btw
# Conflicts: # test/end-to-end/test_simple.py
tests: | ||
- script: build.nu | ||
requirements: | ||
run: |
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.
Wrt to removing nushell
from pixi, would it work if you use build
here, instead of run?
Don't merge pls, i will fix the git test section, i messed up the conflict solving with jetbrains merge tool |
fixed! @wolfv |
closes #1611
i was debating whetever i should add a UTF-8 validation but i thought it should be added just in case for windows computers with asian languages, let me know what you think about it @wolfv
Also, as shown in recipe examples we still hold the requirements/run to not to cause a magicial workflow, because i thought people want to control exactly what they want to run with