This got lost in the other thread so now it has one of its own. 😃
One thing I am still seeing is change detection in git where no changes have been made, seemingly by just by opening the project. I think this could be line-ending stuff? I then noticed that the .gitignore and the .gitattributes files created with the new project are identical. Here's the content of both files:
*.bak
*.*.bak
*.tmp
*.saved.md
~*.*
__*.*
wwwroot/
_docmonster-*/
Should not the .gitattributes look something like this?
# Default: let Git normalize text files (LF in the repo, native on checkout)
* text=auto
# Files that should keep LF even on Windows
*.md text eol=lf
*.sh text eol=lf
# Files that should keep CRLF
*.bat text eol=crlf
*.cmd text eol=crlf
*.prg text eol=crlf
My projects all have a .gitattributes that looks like this:

+++ Rick ---
DM must create both of those automatically when a new project is setup? I will create another new one from the WWHB json and focus on what gets created as far as those git files are concerned.
Yes those are auto-created once when a new project is created.
+++ Rick ---
Then I'll stick to my conclusion that gitattribute is not being created correctly as it is identical to gitignore. At least when importing from WWHB. I don't want to make any assumptions about how/when those files are created.
There was a bug related to the creation of the file, and in some cases that would cause the ignore file to get generated into attributes.
Not sure what path that is, since all my projects have the correct file, but it'll work properly for all scenarios now.
+++ Rick ---
Not to keep this thread going any longer than necessary I'll just reiterate that I created a brand new DM project by importing from WWHB yesterday, and I got exactly what you describe as a bug that was fixed. FWIW my installed version of DM is 0.5.4.5