Your reference 1 already discuss some points about code-review. This answer is primarily based on my experience at work with the Gerrit tool and trunk-based workflow. How would code-review be done? In feature-based model is easy: into the feature branch. In the trunk-based model, since all the commits are published in master, how can I … Read more
git checkout -p $REF — path/to/file e.g., git checkout -p HEAD^ myfile Where $REF is a ref name or commit ID that specifies the commit you want to take the file state from. For example, to selectively revert changes made in the last commit, use HEAD^.
Depends on what you mean by “server”. Git will work happily without a central server, although many teams find it convenient to have a central repository. If by “server”, you mean “install server software”, git will also work (central repository or not) without any special software, through ssh or on the file system. See this … Read more
Great questions and the answer really depends on how you sort your git. The branching model and gitflow in general is trying to give us some order in the chaos that commits are just after a couple of days. The image below shows you what they though makes most sense. (As far as I know … Read more
Changes to your LaTeX workflow: The first step in efficiently managing a Git+LaTeX workflow is to make a few changes to your LaTeX habits. For starters, write each sentence on a separate line. Git was written to version control source code, where each line is distinct and has a specific purpose. When you write documents … Read more
If you like the method in the link you’ve posted, have a look at Git Flow. It’s a set of scripts he created for that workflow. But to answer your question: $ git checkout -b myFeature dev Creates MyFeature branch off dev. Do your work and then $ git commit -am “Your message” Now merge … Read more