![]() Input will checkout as is from the repo but on check in will convert all line endings to LF, just in case a CRLF file was introduced.īy the way I love the WSL I use it every day and do prefer it to using a VM running linux, it works great for node dev.Īnyway back to the main point of this post. If you change the files or create files using a windows editor (I use webstorm and sublime) then you could inadvertently check in windows line endings, so it might be best to use input. WSL behaves like linux so I have the default set which is not to change the line endings going in or out. ![]() I make heavy use of WSL (windows subsystem for linux) as well as centos VMs running on virtualbox. You can also leave as default which is false. On linux it needs to set to false or input as you don’t want files to contain windows line endings during development so you chekout with LF. That is check out windows style (CRLF) but check in linux style (LF). Depending on the OS that you are using you need to ensure that you use the correct setting. This can take three values: true, false and input. ![]() We should all have our git clients set to convert and check in linux line endings which you can check with the command: I don’t know how this happened exactly and didn’t narrow it down to any one commit but just wanted it fixed. We deploy to centos in all our production and pre-prod environments so we always check-in linux line endings.īut recently when I was looking through some codez I found a bit of a mix of files with LF and CRLF line endings and so wanted make them all consistent with the LF linux standard. At work we currently have people who do their dev on linux laptops, linux VMs, windows and the WSL which means that we need to be careful about the compatibility of files in git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |