build: put formatter and linter configs in the root directory

Otherwise, we would have to deal with a custom `--config-path` for every possible formatter on Earth. It's okay to let them clutter the directory (check out other popular repos!). Even if they are visible on the GitHub repo, locally they are hidden by your favorite editor.
azzamsa · Aug 7, 2024 · 60898be · 60898be
1 parent 235d4af
commit 60898be
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 2 deletions.
diff --git a/configs/cliff.toml → .cliff.toml b/configs/cliff.toml → .cliff.toml
diff --git a/configs/typos.toml → .typos.toml b/configs/typos.toml → .typos.toml
diff --git a/justfile b/justfile
@@ -44,7 +44,7 @@ fmt-check:
 [doc('Lint the codebase')]
 lint:
     cargo clippy --all-targets --all-features
-    typos --config configs/typos.toml
+    typos
 
 [doc('Test the codebase')]
 test:
@@ -65,7 +65,7 @@ _doc-check:
 
 [doc('Prepare release hooks')]
 _release-prepare version:
-    git-cliff --config configs/cliff.toml --output CHANGELOG.md --tag {{ version }}
+    git-cliff --config .cliff.toml --output CHANGELOG.md --tag {{ version }}
     just fmt
 
 [doc('Check dependencies health. Pass `--write` to upgrade dependencies')]