Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

"Configuring Git to handle line endings"

What part(s) of the article would you like to see updated?

I feel there is a clarity and/or correctness issue within the sub-section of this page headed "Refreshing a repository after changing line endings".

Specifically:

• The instructions in the numbered list are somewhat unclear as to what exactly is being accomplished, i.e. will the current checked-out version of files' EOL's in the current repo's HEAD be updated, or just the entries in the Git database?
  (I would assume the former given the section's title.)
• The line immediately before the numbered instructions seems to imply you need to manually delete/re-add files from the repo dir at some stage, but if so it's not made clear when this should be done, or if not when during the process it is supposed to occur.
• More importantly, the instruction in point 2 does not work as expected for me when attempting to update the line endings of files in the current repo HEAD for an existing checked-out repo.
  I found an alternative methodology for doing this on Stack Overflow which did work in my case - this thread here, 2nd solution. Would it be possible to add this into the article in some form?
  I am making a pull request with an update to include this in as a possible alternative method under point 2 for my specific use case, but open to suggestions on exact wording!

Additional information

N.B. For my current use case, I am updating the EOL characters in a locally-stored repo, using git version 2.35.1 on Windows, but with the intention to run the code on a Linux system (hence need to force EOL characters to LF).

PR to follow! Thanks.