You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed leaving the README.md and other non-functional files creates a mess of the home directory. But if you would like to add README to your repo, you can move it under .github folder at the root of your repo.
Thanks for the feedback, @kalkayan! I had originally considered doing this, but decided against it b/c I worried that specific name could collide with anyone's choices of having $HOME under version control itself separately. That's not a wise thing to do if you stuff everything, but someone could control $HOME with a suitable .gitignore that's very curated, and thus have a legit need for .github not to be overwritten.
Instead, I chose to put the minimal amount of clutter here: .README and .LICENSE and nothing else (the rest are real dotfiles/dirs).
But ultimately this type of repo isn't meant to be used as-is, rather to be a template for others to heavily edit/adapt to their preferences, so by all means move those over to .github if it fits your workflow better! I can see that being the case for some.
Indeed leaving the README.md and other non-functional files creates a mess of the home directory. But if you would like to add README to your repo, you can move it under
.github
folder at the root of your repo.Refer this - https://stackoverflow.com/questions/60507097/is-there-an-overview-of-what-can-go-into-a-github-dot-github-directory
The text was updated successfully, but these errors were encountered: