caddy/.gitattributes

# shell scripts should not use tabs to indent!
*.bash    text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.sh      text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2

# files for systemd (shell-similar)
*.path    text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.service text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.timer   text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2

# go fmt will enforce this, but in case a user has not called "go fmt" allow GIT to catch this:
*.go      text eol=lf core.whitespace whitespace=indent-with-non-tab,trailing-space,tabwidth=4
go.mod    text eol=lf
go.sum    text eol=lf

*.txt     text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.tpl     text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.htm     text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.html    text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.md      text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
*.yml     text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2
.git*     text eol=auto core.whitespace whitespace=trailing-space
Catch whitespace code style violations locally (#774) Those settings enforce convergence on common coding style with respect to whitespace. Do not use tabs to indent with shell scripts because those tabs most often serve the function of triggering command completion. Which could end a command before it is pasted completely. Traditionally indentation is two spaces here, not four. Other rules will catch stray whitespace at the end of lines or files, which, once committed, would annoy the next developer because his editor would strip them from lines he did not intended to modify in the first place. 2016-04-20 17:56:57 +03:00			`# shell scripts should not use tabs to indent!`
			`*.bash text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.sh text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
Use best practices in build.bash Format of main.buildDate has been locale-dependent, and is now ISO-8601 compliant. Caddy displayed with ```-version``` something like (mind the datetime format): Caddy 0.8.2 (+591b209 Fri Mar 18 21:22:55 UTC 2016) 2 files changed, 9 insertions(+), 4 deletions(-) build.bash main.go which is now: Caddy 0.8.2 (+591b209 2016-03-18 21:22:55Z) 2 files changed, 9 insertions(+), 4 deletions(-) build.bash,main.go See also: * http://wiki.bash-hackers.org/scripting/obsolete * https://google.github.io/styleguide/shell.xml * https://xkcd.com/1179/ 2016-03-19 01:10:24 +03:00
Catch whitespace code style violations locally (#774) Those settings enforce convergence on common coding style with respect to whitespace. Do not use tabs to indent with shell scripts because those tabs most often serve the function of triggering command completion. Which could end a command before it is pasted completely. Traditionally indentation is two spaces here, not four. Other rules will catch stray whitespace at the end of lines or files, which, once committed, would annoy the next developer because his editor would strip them from lines he did not intended to modify in the first place. 2016-04-20 17:56:57 +03:00			`# files for systemd (shell-similar)`
			`*.path text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.service text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.timer text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`

			`# go fmt will enforce this, but in case a user has not called "go fmt" allow GIT to catch this:`
			`*.go text eol=lf core.whitespace whitespace=indent-with-non-tab,trailing-space,tabwidth=4`
gitattributes: go.mod, go.sum always eol=lf (#2753) 2019-09-22 23:17:16 +03:00			`go.mod text eol=lf`
			`go.sum text eol=lf`
Catch whitespace code style violations locally (#774) Those settings enforce convergence on common coding style with respect to whitespace. Do not use tabs to indent with shell scripts because those tabs most often serve the function of triggering command completion. Which could end a command before it is pasted completely. Traditionally indentation is two spaces here, not four. Other rules will catch stray whitespace at the end of lines or files, which, once committed, would annoy the next developer because his editor would strip them from lines he did not intended to modify in the first place. 2016-04-20 17:56:57 +03:00
.txt, .tpl, .htm, .html, *.md should always use eol=lf (#2345) 2018-11-17 19:24:54 +03:00			`*.txt text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.tpl text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.htm text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.html text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`*.md text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
Catch whitespace code style violations locally (#774) Those settings enforce convergence on common coding style with respect to whitespace. Do not use tabs to indent with shell scripts because those tabs most often serve the function of triggering command completion. Which could end a command before it is pasted completely. Traditionally indentation is two spaces here, not four. Other rules will catch stray whitespace at the end of lines or files, which, once committed, would annoy the next developer because his editor would strip them from lines he did not intended to modify in the first place. 2016-04-20 17:56:57 +03:00			`*.yml text eol=lf core.whitespace whitespace=tab-in-indent,trailing-space,tabwidth=2`
			`.git* text eol=auto core.whitespace whitespace=trailing-space`