Enregistrement.2025-12-11.224758.1.mp4
To ensure the stability of the master branch and maintain a clear history, please strictly follow this process for all new features or modifications.
Never work directly on the master branch.
All new development must begin by creating a new descriptive branch from master. The naming convention is feature-.
git checkout master
git pull origin master
git checkout -b feature-my-awesome-feature
Work and make your commits on your feature-... branch.
Be specific in your commit messages. A good commit message explains what you did and (if necessary) why.
Bad commit:
git commit -m "Update"
Good commit:
git commit -m "Feat: Add player collision detection"
When your feature is complete, tested, and working:
Switch back to the master branch.
Merge your feature branch into master.
Push the updated master branch to the remote repository (GitHub).
Bash
git checkout master
git merge feature-my-awesome-feature
git push origin master
Once your branch has been successfully merged into master, close it (delete it) to keep the repository clean.
Bash
git branch -d feature-my-awesome-feature
git push origin --delete feature-my-awesome-feature
dotnet tool install -g dotnet-mgcb
dotnet mgcb-editor