0

This question already has an answer here:

In teams, when should one get the latest versions of the files in source control in an optimal workflow?

For example, should it be right before you commit? Or every morning? Should it be automated?

In my current team we have no guidelines about this, occasionally leading to situations of e.g. people not being able to build, or other problems. I'd like to prevent this.

marked as duplicate by gnat, Community May 23 '18 at 11:21

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • as a side note, question as currently presented feels incredibly broad – gnat May 23 '18 at 11:09
  • If some of the answers to that question answer this question, does that mean its a duplicate? If I ask about the flatness of the earth, and someone answers it in an answer to a question about the size of the moon, are those questions duplicates? – Protector one May 23 '18 at 11:15
  • see explanation here: " the proof is in the answers... Neither the person asking nor the person who lands from Google cares if the question has been asked before: they care if it has been answered..." – gnat May 23 '18 at 11:19
  • dvcs or cvcs? (it can make a difference) – jk. May 23 '18 at 11:20
  • 1
    @Protectorone for dvcs you are free to commit independently of pull/push for cvcs you aren't so must always update + merge/rebase before commit/push. both tend to work better with regular pulls/updates – jk. May 23 '18 at 11:46