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.

Sign up for GitHub

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

Jump to bottom

Scripts are not executable when cloned into hosts that use CRLF endings #291

Closed
glennmusa opened this issue Jul 13, 2021 · 0 comments · Fixed by #292
Closed

Scripts are not executable when cloned into hosts that use CRLF endings #291

glennmusa opened this issue Jul 13, 2021 · 0 comments · Fixed by #292
Assignees
@glennmusa

Comments

@glennmusa
Copy link
Contributor

Benefit/Result/Outcome
If I clone the repository from Windows, then open the .devcontainer, I will be able to execute the BASH scripts in the repository.

Description
Today, if I clone down to Windows and have CRLF endings (the default behavior), when I try to execute the BASH scripts from within the .devcontainer served from the Windows disk space I'll get script execution errors.

It shouldn't matter where I clone the scripts, they should be executable from within the container.

Acceptance Criteria

  • Configure the repository to set all *.sh as text files with LF endings
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@glennmusa glennmusa

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

update .gitattributes to use LF endings for *.sh Azure/missionlz
1 participant
@glennmusa