title: Postman changing line endings when exporting JSON collection file from CR LF (Windows) to LF (Unix)
body: <p><strong>Issue</strong></p>
  <p>Postman is changing line endings when exporting a JSON collection file from CR LF (Windows) to LF (Unix) and this is a causing Warning when I try to commit the file to git.</p>
  <p>Has anyone come across this before and is there a solution other than the work around that I outline below?</p>
  <p><strong>Specs</strong></p>
  <ul>
  <li>Windows 10</li>
  <li>Postman version 8.0.3</li>
  <li>Notepad++ version 7.9.1</li>
  </ul>
  <p><strong>Steps to reproduce</strong></p>
  <ul>
  <li><p>Ensure Postman collection JSON file has CR LF (Windows) line endings using Notepad++ as shown in screen grab 1</p>
  </li>
  <li><p>Import Postman collection file to Scratchpad Workspace</p>
  </li>
  <li><p>Make a small change like rename a Request (this is automatically saved)</p>
  </li>
  <li><p>Export the collection and save/replace it back to the original file that was imported</p>
  </li>
  <li><p>Go back to Notepad++ and you will be asked to reload the file, which you &quot;yes&quot; to</p>
  </li>
  <li><p>Check that the Postman collection JSON file has now unexpectedly changed  CR LF (Windows) line endings to LF (Unix) line endings using Notepad++ as shown in screen grab 1</p>
  </li>
  <li><p>Stage the file in git and you will see the Warning in screen grab 2. Note, I'm using Git Extensions here but you will see the same Warning on the command line.</p>
  </li>
  </ul>
  <p><strong>.gitattributes</strong></p>
  <p>My .gitattributes file has the following entries:</p>
  <pre><code>* text=auto encoding=UTF-8
  *.sh text eol=lf
  *.service text eol=lf
  </code></pre>
  <ul>
  <li>text=auto encoding=UTF-8 is setting the default behaviour of text/JSON files</li>
  </ul>
  <p><strong>Work around</strong></p>
  <p>To avoid the Warning, I have to do the following every time I want to change/export and git commit a Postman collection file, which I'm sure I shouldn't need to do. (A colleague of mine has the same behaviour when I checked on his machine).</p>
  <ul>
  <li><p>After Steps to reproduce above, un-stage the file in git</p>
  </li>
  <li><p>Use Notepad++ to change the Postman file back from having LF (Unix) line endings to having CR LF (Windows) line endings using Notepad++</p>
  </li>
  <li><p>Save the file in Notepad++</p>
  </li>
  <li><p>Stage the file in git and the Warning will have gone</p>
  </li>
  </ul>
  <p><strong>Screen grabs</strong></p>
  <p>Screen grab 1</p>
  <p><a href="https://i.stack.imgur.com/CX8hM.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CX8hM.png" alt="enter image description here" /></a></p>
  <p>Screen grab 2</p>
  <p><a href="https://i.stack.imgur.com/FjRwc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/FjRwc.png" alt="enter image description here" /></a></p>
  <p><strong>Links</strong></p>
  <p><a href="https://stackoverflow.com/questions/5834014/lf-will-be-replaced-by-crlf-in-git-what-is-that-and-is-it-important">LF will be replaced by CRLF in git - What is that and is it important?</a></p>
  <p><a href="https://stackoverflow.com/questions/17628305/windows-git-warning-lf-will-be-replaced-by-crlf-is-that-warning-tail-backwar">Windows git &quot;warning: LF will be replaced by CRLF&quot;, is that warning tail backward?</a></p>
  <p><a href="https://github.com/postmanlabs/postman-app-support/issues/190" rel="nofollow noreferrer">https://github.com/postmanlabs/postman-app-support/issues/190</a></p>
  <p><a href="https://github.com/postmanlabs/postman-app-support/issues/726" rel="nofollow noreferrer">https://github.com/postmanlabs/postman-app-support/issues/726</a></p>
  <p><a href="https://github.com/postmanlabs/postman-app-support/issues/4179" rel="nofollow noreferrer">https://github.com/postmanlabs/postman-app-support/issues/4179</a></p>