diff --git a/app/page.tsx b/app/page.tsx index 279ddca..4721c8d 100644 --- a/app/page.tsx +++ b/app/page.tsx @@ -3,7 +3,7 @@ import Image from "next/image"; export default function Home() { return (
-
wow
+
husky test
test husky 123

diff --git a/docs/BRANCH_MANAGEMENT.md b/docs/BRANCH_MANAGEMENT.md index b39c6eb..c91742a 100644 --- a/docs/BRANCH_MANAGEMENT.md +++ b/docs/BRANCH_MANAGEMENT.md @@ -13,31 +13,31 @@ ## 1. Branch Structure Overview -- Main Branch (main) +- Main Branch (`main`) - Represents the stable version of the project. - Code must undergo a pull request (PR) and pass code reviews. - Only merges from: - - release - - doc -- Documentation Branch (doc) + - `release` + - `doc` +- Documentation Branch (`doc`) - Used exclusively for documentation. - Cannot merge from any other branches. -- Release Branch (release) +- Release Branch (`release`) - Contains stable code ready for delivery. - Code must undergo a pull request (PR) and pass code reviews. - - Only merges from feature/\* branches. -- Feature Branches (feature/\*) + - Only merges from `feature/*` branches. +- Feature Branches (`feature/*`) - Used for specific feature development. - Developers pull the latest code from main or release as needed. - Can be organized as: - - feature/ - - feature/- + - `feature/` + - `feature/-` - Periodically merges into release. -- Test Branches (test/\*) +- Test Branches (`test/*`) - Used for testing specific aspects of the project. - Should not merge into any other branch but can receive merges. -> protected branches: main, release +> protected branches: `main`, `release` ## 2. Best Practices