Skip to content
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

Updated hashbang and permissions for shell scripts #76

Merged
merged 1 commit into from
Jul 13, 2024

Conversation

djbelyak
Copy link
Contributor

Git is tracking file permissions, so using chmod +x in shell scripts is redundant. To make a shell script executable, it's enough to execute chmod +x and commit the file. On Windows, it's possible to use the next command:

git update-index --chmod=+x <path_to_shell>

The source command is not compatible with sh specification, thus hash-bang points to bash. All scripts touched for consistency.

Git is tracking file permissions, so using chmod +x in shell scripts is redundant.
To make a shell script executable, it's enough to execute chmod +x and commit the file. On Windows, it's possible to use the next command:
git update-index --chmod=+x <path_to_shell>

The source command is not compatible with sh specification, thus hash-bang points to bash. All scripts touched for consistency.
@dzhdanNV dzhdanNV merged commit 301cc8c into NVIDIAGameWorks:main Jul 13, 2024
2 checks passed
@dzhdanNV
Copy link
Collaborator

Thanks (again), Ivan!

@djbelyak djbelyak deleted the sh-permissions branch July 16, 2024 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants