New repository behaviour doesn't match GitHub.com

Description

When creating a new repository through GitHub Desktop with the settings shown below an “Initial commit” gets made for you, adding a default .gitattributes file (which has no new line for whatever reason). However, when you create one through GitHub.com with the same settings you get a blank repository to work with. Personally I prefer it to be completely blank, I understand that this commit can be undone straight away but it seems strange to have it different than GitHub.com.

---

Version

GitHub Desktop version: 1.0.6

OS version: Windows 10 Home 10.0.15063 - Build 15063

---

Steps to Reproduce

1. Create a new repository on GitHub.com with the settings shown below.
2. Create a new respository through GitHub desktop with the settings shown below.
3. See the “Initial commit” that only gets made on the second repository.

Expected behavior: A blank repository with no commits.

Actual behavior: A repository already containing an “Initial commit”.

Reproduces how often: 100%

---

Additional Information

[shiftkey]

not that I’m familiar with any of that but I’m sure if there’s a reason it’s a good one.

Probably the best summary of Git and line endings (and how we ended up with .gitattributes) is this piece by @tclem: “Mind the End of Your Line”. Have a read of that when you get a chance.

[joshaber]

Yes, unfortunately line endings are thorny 😱

I’ve noticed that if for example I make a .gitattributes ahead of time in my project’s folder (before it’s been initialized) and then create a new repository using desktop within that folder it will overwrite my existing one with the default, is that intended too?

Hmm that sounds like a bug. Would you mind opening an issue specifically about that?