chore: move rules to root

2025-12-12 06:20:09 +01:00 · 2024-12-08 21:13:22 +01:00 · 2024-12-08 21:13:22 +01:00 · 0c7277f910
commit 0c7277f910
parent 79264e1a4e
18 changed files with 2 additions and 2 deletions
--- a/core/rules
+++ b/core/rules
@ -0,0 +1 @@
+../rules
--- a/1
+++ b/1
@ -1 +0,0 @@
-core/rules
--- a/rules.md
+++ b/rules.md
@ -1,6 +1,6 @@
 # Writing Rules

-Rule files placed under [rules](./core/rules) in the project directory are parsed at compilation, everything is parsed to Rust code before compiling. You don't have to know the project structure nor Rust to write blazing fast rules!
+Rule files placed under [rules](./rules) in the project directory are parsed at compilation, everything is parsed to Rust code before compiling. You don't have to know the project structure nor Rust to write blazing fast rules!

 For compile-time rules, if only rules are changed, cargo won't recompile the project because Rust code were intact. You will have to notify it manually by:
 ```shell
--- a/core/rules/c_typo.toml
+++ b/core/rules/c_typo.toml
--- a/core/rules/cargo.toml
+++ b/core/rules/cargo.toml
--- a/core/rules/cat.toml
+++ b/core/rules/cat.toml
--- a/core/rules/cd.toml
+++ b/core/rules/cd.toml
--- a/core/rules/cp.toml
+++ b/core/rules/cp.toml
--- a/core/rules/git.toml
+++ b/core/rules/git.toml
--- a/core/rules/mkdir.toml
+++ b/core/rules/mkdir.toml
--- a/core/rules/mv.toml
+++ b/core/rules/mv.toml
--- a/core/rules/npm.toml
+++ b/core/rules/npm.toml
--- a/core/rules/pacman.toml
+++ b/core/rules/pacman.toml
--- a/core/rules/pr_general.toml
+++ b/core/rules/pr_general.toml
--- a/core/rules/pr_privilege.toml
+++ b/core/rules/pr_privilege.toml
--- a/core/rules/rm.toml
+++ b/core/rules/rm.toml
--- a/core/rules/touch.toml
+++ b/core/rules/touch.toml
--- a/core/rules/yarn.toml
+++ b/core/rules/yarn.toml