Update 'Development workflow'

2022-05-11 12:48:50 +00:00
parent 01cbb542d7
commit b711e51bd3
1 changed files with 13 additions and 0 deletions
@@ -2,8 +2,21 @@
 <br><br>**You have identified a bug and it's fix.   What if minos could fly?  You found something not following 24.3 rules.  Perhaps you want to try and morph your MagicBox into a League of Legends clone.**
 <br><br>This document will describe the workflow involved in turning your ideas into reality; intended either for the Magicbane production server or on your personal Magicbox.  With Magicbane technology effecting change has never been easier.

+### Branch or Fork?
+
+A branch should be made for a small group of related changes.  
+
+**One Bug == One Branch. <br>
+One Feature == One Branch.**
+
+A fork is a complete copy of the codebase.  If your desire is to morph Magicbane into a LOL clone it would require dozens of separate branches.  Fork the repo when you want to perform major surgery.
+
+**Fork == Major changes consisting of many branches.**
+
 ### A new branch

+For the purpose of this tutorial let us create a new branch.
+
 In the lower right hand corner of the IDE will be displayed the current branch that is checked out from the repository.  The branch **master** reflects the current codebase running in production.  All new branches should be sourced from origin/master.

 ![currentbranch](https://media.discordapp.net/attachments/534260038039109632/970609379248340992/unknown.png)