David Aldrich <david.aldrich.n...@gmail.com> writes:

Hi, I am just getting started with Git. Our organization uses Subversion and we are thinking of moving to Git for new projects. I think it will be crucial to standardize on an agreed branching workflow, which should be as simple as possible.

With Subversion, most of our development is on trunk, but we do use branches for features or personal work. We tend not to use release

I have seen various workflow types. For example, GitLab documentation briefly describes Centralized, Feature branching and Trunk-based development workflows (though I can't quite see the difference between Centralized and Trunk-based). But there doesn't seem to be an
explanation of the commands needed for each workflow.

Would it be possible to have a recommendation for a workflow and to point me to an implementation of it? That is, I am hoping to see Git
commands for the various stages of the workflow.

If the workflow you are using today in SVN is good enough, why not simply start there? It could be the least possible interruption and ease adoption. Then as you and the rest of the organisation gains experience and get more comfortable with git you can start modify the workflow as you go along.


Magnus Therning                   OpenPGP: 0x927912051716CE39
email: mag...@therning.org
@magthe@mastodon.technology       http://magnus.therning.org/

"Zaphod grinned two manic grins, sauntered over to the bar and bought
most of it."

— Zaphod in paradise.

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.
To view this discussion on the web visit 

Attachment: signature.asc
Description: PGP signature

Reply via email to