🌍
English
Differences
This shows you the differences between two versions of the page.
|
dev:core:git [2014/11/07 10:08] mistic100 created |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | <WRAP round tip> | ||
| - | This is a work in progress, all concepts exposed here are susceptible. | ||
| - | </WRAP> | ||
| - | |||
| - | ====== Git workflow and best pratices ====== | ||
| - | |||
| - | ===== Reminder ===== | ||
| - | |||
| - | On Piwigo we typically have two active branches: | ||
| - | * ''master'' holds the main source code with features for the next major version | ||
| - | * ''2.7'' (in instance) holds the source code of the current major version, only bug fixes and minor features are pushed to this branch | ||
| - | |||
| - | As the SVN concept of branches is very loose we used to develop either on ''master'' or ''2.7'' and then merge specific commits to the other branch if needed. This concept is totally applicable in Git, it's called **cherry pick**. | ||
| - | |||
| - | **But this is not how Git is supposed to work.** Git tends to track every changes, and links them to others, and because **cherry pick** basically forge a new commit from another one, a part of the history is lost. | ||
| - | |||
| - | ===== Workflow ===== | ||
| - | |||
| - | First of all I advise your to read this excellent article which became a reference: [[http://nvie.com/posts/a-successful-git-branching-model|A successful Git branching model]]. | ||
| - | |||