The CLI is quite straight forward, but we will do a quick rundown of all the options here.
Solo Repo Controls:
1. Create an 'exp' branch
-Generates the exp branch copying all files from the main directory to the exp directory for you to
do your work and be able to test your work without compromising the main branch.
2. Merge the exp branch with the main branch
-Pretty self-explainitory, alsos generates a backup file to roll back to.
3. Roll back the exp branch to the previous main version
-Rolls back to said roll back generated above, if you have multiple versions to go back to - it supports choosing which one.
4. Roll forward to the last exp branch that was pushed to main
Rolled back but want to go forward/undo the rollback? This handles it, when you roll back the exp branch - as you had it prerollback is saved for you to go forwards to.
Collaborative Repo Controls (user):
5. Prep the repo for collaboration
Creates the collab branch (directory) . This is the folder you allow access to on your FTP sure to allow collaborators to upload to.
6. Submit your changes to the exp branch (copies your exp directory with the collab)
Pretty self-explainitory, copies your exp branch to the collab branch & also generates a backup file to roll back to
Collaborative Repo Controls (Admin):
7. Accept Collab (merges the collab into the exp)
For the administrators of the project ~ This merges the collaborators submitted collab branch into your exp branch
8. Roll back the 'exp' branch to the previous version (undo collab merge)
Undo the merge/go back to any saved rollback
9. Roll back the 'collab' branch to the previous version(redo collab merge)
Redo the merge/go to any saved future