Community mailing list archives
Re: Gitflow BangBangby
Hi!If you where attracted by the subject, you might be interested in a discussion with the final goal to figure out, how to implement gitflow within the odoo ecosystem and branch-naming standards. I know, decisions have been made during the move to github, so let's look if we might end up challenging them or not...From a first sight, I think it is perfectly possible to implement the gitflow tool for odoo. http://danielkummer.github.io/git-flow-cheatsheet/Note that it is possible to adapt its configuration: https://github.com/nvie/gitflow/wiki/Config-valuesAs configuration changes depending on which branch we are, we need to pass "branched" configuration. How?The file .gitconfig comes in handy. An example: https://gist.github.com/pksunkara/988716#file-gitconfig-L46What does this mean, we could make an incremental (small) change to the odoo-ecosystem branch design and have a HUGE impact on developer friendliness and elegantly bypassing tedious fundamentals in the contribution learning curve.Any allies to push this forward?Things to be done:- carefully design .gitconfigs (which could do other good) per official odoo-branch-- side note: such as configuring upstream doesn't actually need a python script or such :)- promote this link: http://danielkummer.github.io/git-flow-cheatsheet/Saludos CordialesDavid Arnold
David Arnold BA HSG / Analista
315 304 13 68/ firstname.lastname@example.org
devCO - empresa de consultoría de sistemas (en fundación)
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.