shell-things/.gitattributes

# See https://www.git-scm.com/docs/gitattributes#_effects for more information
*	text=auto eol=lf linguist-detectable

# These files are scary, let's not touch them
LICENSE	text lockable
CITATION.cff	text lockable

# Windows files even in checkout
# Ref: https://rehansaeed.com/gitattributes-best-practices/#line-endings
*.{reg,[rR][eE][gG]}	text eol=crlf
*.{bat,[bB][aA][tT]}	text eol=crlf
*.{ahk,[aA][hH][kK]}	text eol=crlf
.{editorconfig,gitattributes,pre-commit-config.yaml}: add comment to beginning for more details I know what the files do, but do my readers? Especially when I am using these files as templates for new repositories? 2023-05-19 19:35:05 +02:00			`# See https://www.git-scm.com/docs/gitattributes#_effects for more information`
.gitattributes: tab 2023-02-21 14:35:31 +01:00			`* text=auto eol=lf linguist-detectable`
.gitattributes: lock CITATION & LICENSE 2023-02-21 14:34:29 +01:00
			`# These files are scary, let's not touch them`
			`LICENSE text lockable`
			`CITATION.cff text lockable`

simplify gitattributes & Windows/.gitattributes 2023-02-12 09:30:18 +01:00			`# Windows files even in checkout`
			`# Ref: https://rehansaeed.com/gitattributes-best-practices/#line-endings`
.gitattributes: tab 2023-02-21 14:35:31 +01:00			`*.{reg,[rR][eE][gG]} text eol=crlf`
			`*.{bat,[bB][aA][tT]} text eol=crlf`
			`*.{ahk,[aA][hH][kK]} text eol=crlf`