Skip to content

Line endings guidance for contributors #171

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

Merged
merged 3 commits into from
Mar 17, 2021
Merged

Line endings guidance for contributors #171

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
94a70c6
#
pdeschain Mar 15, 2021
b13a3ff
Sam's comments
pdeschain Mar 16, 2021
7cd1795
Update CONTRIBUTING.md
pdeschain Mar 17, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,4 +53,9 @@ Always write a clear log message for your commits. One-line messages are fine fo

$ git commit -m "A brief summary of the commit
>
> A paragraph describing what changed and its impact."
> A paragraph describing what changed and its impact."

### Line Endings Guidelines
The project is using Unix-style line endings.

Follow the instructions in the official [Git Configuration](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) documentation, the [Formatting and Whitespace](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#_formatting_and_whitespace) section, to enable `autocrlf` setting on your machine.