A project is being developed, new people are being added to the team. Versioning is done using GIT. Explain the algorithm for connecting a new person to the project. Suppose the last commit is called second.

  1. A new branch is created for a new developer.
  2. It clones the project repository.
  3. Moves to its branch

Question 1: Do I understand correctly the algorithm for adding a new developer to a project?

Question 2: After cloning, the new developer starts his work, in his branch, with commit second?

    1 answer 1

    No need to create a specific branch for the developer. This is counterproductive.

    The branches are created by developers under features (tasks / bugs). Normally, when there are several long-lived branches (master / develop) and many short-lived tasks.

    and also here on the site :)

    • one
      But such an option is also possible: gitlab.i-free.com/m.ivanov/gitmem/wikis/home (it starts with the fact that each developer has his own clone of the master) - PinkTux
    • Considering that each developer clones his own repository, everyone will have “his master” :) - KoVadim
    • @KoVadim, several developers work under one branch to solve one problem? So? - bsuart
    • one
      No, this is not a clone in the sense obtained with the help of git clone , namely its fork of the master branch on a remote server, which for this developer is considered a master / upstream. Something enters the master master only after pushing it into its copy of the master and accepting a merge-request from it. - PinkTux
    • 2
      @ bsart2017 usually one developer is working on the same task. And he creates a branch for himself. When the work is completed - merzhit in the master / develom. - KoVadim