PUBLIC MARKS with tags workflow & git

Version management with git makes branching and merging much easier than older versioning systems such as SVN. This allows a wide variety of branching strategies and workflows. Almost all of these are an improvement over the methods used before git. But many organizations end up with a workflow that is not clearly defined, overly complex or not integrated with issue tracking systems. Therefore we propose the GitLab flow as clearly defined set of best practices. It combines feature driven development and feature branches with issue tracking.

A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model.

A very well explained and detailed workflow for branching with git.

A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model.

A git workflow when working alone on a project. Interesting use of git rebase to prevent merge conflicts. This workflow is intended for one person: rebasing on a branch is messy if someone else has a copy of it.

Use git branches as patches: if you have a master and a dev branches, create a new X branch from master (the prod branch), commit, merge into dev with the --no-ff option, and when if it works as expected, merge the X branch into the master.

Basic workflow for maintaining a blog using Git: a local repository, a remote repository (and a bare) and some hooks to sync the repos and generate the blog.

Workflow for the git submodules.

Marche à suivre pour utiliser Google Code en tant que miroir d'un projet Git.