[Openerp-community] git: branch names
Hello, I've noticed that git offers hierarchic branch names, and I think this could be a useful tool for the management of branches and PR. https://github.com/odoo-dev/odoo/branches seems to be using a flat namespace similar to what was used in Launchpad, but I feel that this could be vastly improved. Are there any github old timers who could point us to the state of the art best practices here? I've seen http://stackoverflow.com/questions/273695/git-branch-naming-best-practices and I like the username/feature/issue-tracker-number/short-description scheme. Maybe a version number for the target branch should be added somewhere. Opinions? -- Alexandre Fayolle Chef de Projet Tel : + 33 (0)4 79 26 57 94 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] git: branch names
Slashes in git branch names can cause problems with some helper tools as it messes up the .git/refs/ directory. The username and feature/fix/i18n part seems redundant to me, these belong in commit messages and PR descriptions. The issue tracker number can be put in the commit message: i.e. Fixes #24. The advantage of this when the PR is merged, github should automatically close #24. version-number-short-description should be good enough IMHO. Le mardi 10 juin 2014 à 14:49 +0200, Alexandre Fayolle a écrit : Hello, I've noticed that git offers hierarchic branch names, and I think this could be a useful tool for the management of branches and PR. https://github.com/odoo-dev/odoo/branches seems to be using a flat namespace similar to what was used in Launchpad, but I feel that this could be vastly improved. Are there any github old timers who could point us to the state of the art best practices here? I've seen http://stackoverflow.com/questions/273695/git-branch-naming-best-practices and I like the username/feature/issue-tracker-number/short-description scheme. Maybe a version number for the target branch should be added somewhere. Opinions? signature.asc Description: This is a digitally signed message part ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
Re: [Openerp-community] git: branch names
On 06/10/2014 04:08 PM, Sandy Carter wrote: Slashes in git branch names can cause problems with some helper tools as it messes up the .git/refs/ directory. That's exactly why we have decided to avoid it ;-) ___ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
