Univers42
diff --git a/‎README.md‎
Lines changed: 10 additions & 0 deletions b/‎README.md‎
Lines changed: 10 additions & 0 deletions
diff --git a/‎incs/ast.h‎ b/‎incs/ast.h‎
diff --git a/‎incs/builtins.h‎ b/‎incs/builtins.h‎
diff --git a/‎incs/env.h‎ b/‎incs/env.h‎
diff --git a/‎incs/executor.h‎ b/‎incs/executor.h‎
diff --git a/‎incs/expander.h‎ b/‎incs/expander.h‎
diff --git a/‎incs/globbing.h‎ b/‎incs/globbing.h‎
diff --git a/‎incs/lexer.h‎ b/‎incs/lexer.h‎
diff --git a/‎incs/parser.h‎ b/‎incs/parser.h‎
diff --git a/‎incs/signals.h‎ b/‎incs/signals.h‎
@@ -2,6 +2,16 @@
 To be efficient we must agree to respect different rules of organization to set
 this project the most quickly and reliably possibly. Thoses framework pass by acknowledging different set of rules.
 
+# Before we even code a line
+- [ ] Git Workflow
+- [ ] Hooks
+- [ ] CI (GitHub Actions)
+- [ ] Code Style
+- [ ] Commit convention
+- [ ] branch protection
+- [ ] Docs
+- [ ] interactive rebase habits
+
 ## Commit
 
 From What I've sawn on the internet, most teams follow some variation of these three pillars: