> On Jan 28, 2015, at 11:48 PM, Mark Struberg <strub...@yahoo.de> wrote: > > Alan, the gitflow way is basically review then commit. Because the 'Release > Manager' (of whom we lack...) needs to review and choose (cherry-pick) EACH > AND EVERY SINGLE COMMIT.
Where do you see that? I keep reading that Atlasssian document and I don’t see where it requires cherry picking each and every commit. > And even worse - by deleting the 'temp' branch afterwards we also loose all > the other work later. > > And once again: > > We must not delete anything from our repos! > > We must not squash commits! > > We must not loose any history! > We must guarantee a verifyable code provenance! > > Those are no 'should' those are MUST! You guys must be reading something different than I am or I am accidentally skimming over some critical bit: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow <https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow> Can you point me to the parts that justify your allegations? Regards, Alan
