.{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?
This commit is contained in:
Aminda Suomalainen 2023-05-19 20:35:05 +03:00
parent 29d783647b
commit f77e15eb68
Signed by: Mikaela
SSH Key Fingerprint: SHA256:CXLULpqNBdUKB6E6fLA1b/4SzG0HvKD19PbIePU175Q
3 changed files with 4 additions and 0 deletions

View File

@ -1,3 +1,4 @@
# See https://editorconfig.org for more information
# Note: I use this file as ~/.editorconfig when something doesn't specify to # Note: I use this file as ~/.editorconfig when something doesn't specify to
# be root before reaching ~, so this contains files not seen in this repo # be root before reaching ~, so this contains files not seen in this repo
root = true root = true

1
.gitattributes vendored
View File

@ -1,3 +1,4 @@
# See https://www.git-scm.com/docs/gitattributes#_effects for more information
* text=auto eol=lf linguist-detectable * text=auto eol=lf linguist-detectable
# These files are scary, let's not touch them # These files are scary, let's not touch them

View File

@ -1,3 +1,5 @@
# See https://pre-commit.com for more information
# See https://pre-commit.ci for more information
ci: ci:
# Attempts to use networking and fails at name resolution, local hook # Attempts to use networking and fails at name resolution, local hook
# skip: [bundler-audit, pylint] # skip: [bundler-audit, pylint]