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
Friendlier vibes.
I want computing to be cosy.
GitHub recognizes these just as well (e.g. for the "About" links on a repo's home page): https://github.com/tfiers/gh-behaviour-testing
GitHub does the same thing. (This is from another place where these files are linked: starting a new discussion thread:)
The text was updated successfully, but these errors were encountered:
I won't die on this hill, but I personally find it useful to "filter out" any filenames with ALL_CAPS, because I know they are not related to code. Makes it easier to parse the project IMO. There's also something to be said for following conventions, but it's not so important in this case.
If my "filtering" argument hasn't convinced you, then I'm also OK with switching!
total bikeshed:
Current Situation
markdown filenames are in all caps (CODE_OF_CONDUCT.md, LICENSE.md, README.md, CONTRIBUTING.md, ..)
Enhancement
PascalCase (if readable) or upper Kebab-Case: Code-of-Conduct.md, License.md, ReadMe.md, Contributing.md, ..
Reasoning
Friendlier vibes.
I want computing to be cosy.
GitHub recognizes these just as well (e.g. for the "About" links on a repo's home page): https://github.com/tfiers/gh-behaviour-testing
GitHub does the same thing. (This is from another place where these files are linked: starting a new discussion thread:)
The text was updated successfully, but these errors were encountered: