From f77e15eb68e5c497a3d7b8f77bee952cae5ad52e Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Fri, 19 May 2023 20:35:05 +0300 Subject: [PATCH] .{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? --- .editorconfig | 1 + .gitattributes | 1 + .pre-commit-config.yaml | 2 ++ 3 files changed, 4 insertions(+) diff --git a/.editorconfig b/.editorconfig index 89b65b68..8ca6d5b1 100644 --- a/.editorconfig +++ b/.editorconfig @@ -1,3 +1,4 @@ +# See https://editorconfig.org for more information # 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 root = true diff --git a/.gitattributes b/.gitattributes index 8dd96a75..e2a4aa58 100644 --- a/.gitattributes +++ b/.gitattributes @@ -1,3 +1,4 @@ +# 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 diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 1b038689..5ffd64fb 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -1,3 +1,5 @@ +# See https://pre-commit.com for more information +# See https://pre-commit.ci for more information ci: # Attempts to use networking and fails at name resolution, local hook # skip: [bundler-audit, pylint]