yeofrancis / SCM-with-Git-Branching

7 stars 0 forks source link

Branching Strategy

User Story :

A 3-months new start-up with 2 small group of developers handling separately Frontend and Backend development. The company have also started to look into mobile app and is forming a mobile app developer team. The company have been using Git, and want to have a more organise and structure process in Source Code Management. The DevOps team is tasked to set up an appropriate SCM framework taking into the below considerations:

Which strategy should I use??😕 \ Kindly provide your comment....Thanks.🙏 \ There are several approaches:

GitFlow\ GitHub Flow\ GitLab Flow\ OneFlow

The 10 Basic Commands of Git that I use

  1. git add .\ tell git to add or include all files in the next commit
  2. git commit -m "descriptions"\ takes all added files and commits them to project history
  3. git push\ move all committed changes to remote repository.
  4. git status\ display current status of working directory
  5. git clone \ make a duplicate of an existing Git repository
  6. git checkout -b \ create a new branch on your local machine and open it
  7. git branch -d delete a branch on your local machine
  8. git pull\ get all changes from the remote to your local copy
  9. git merge \ integrate all changes from another branch into yours
  10. git stash\ stores uncommitted changes for use latter and subsequently reverts them from your working copy

    These help me alot in my git process, kindly give me a star if this have help you in one way or another, Thanks. 😘