FWIW, we have a multi-national dev team, not as large as yours though, and we spend time _using_ Git every day obviously but I wouldn't say we spend hardly any time "sorting out Git issues", if by that you mean figuring out what Git is doing as opposed to using it to get our work done. So I wouldn't say it's normal to spend that much time, no.
On Wed, 2017-01-11 at 22:14 -0800, AD S wrote: > Sometimes when I push to the remote repo, only some of the files > appear. However, if I push to Github I can see them all appearing > fine. This is an interesting comment. Does this mean you're using multiple remotes in your work? That wasn't clear to me before. If true it could be one reason for issues; multiple remotes are of course a hallmark of a DVCS like git, but it does increase the potential to get something wrong if you're not clear on how it all works. If you run: git remote -v do you see multiple push/fetch remotes? I suspect that your environment doesn't have a very well-defined workflow, or at least not one that's explained well enough. It could even be that the "simple CLI" you're using is buggy and actually _causing_ problems: it's not uncommon for people who write those to miss corner cases etc. that break things and, because it's a script, it will keep going and mess things up further. > Perhaps I am thinking of it wrongly - I always thought Git was a kind > of 'helper' tool that ran in the background. Hm, well, not literally of course. Git is a command line tool, like "ls" or whatever, that runs when you type a git command; it doesn't run in the background. You type the command, git runs, then it finishes the command you typed and exits and you get your shell prompt back. In many ways Git is a facilitator of distributed version control: it doesn't really have a preferred "right" way to do version control. It supports almost any workflow you want to use... someone (who knows what they're doing) needs to define the workflow that works for your environment. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
