What techniques to use to remember to merge develop to master after a release using Gitflow?

Hello there,

Got an issue at work where people are forgetting to merge develop to master after going live with new features.

We are looking for a way to remember to merge develop to master after our new release goes to production. We don't ship to production on a regular basis, so it's once in a while.

Do you have any suggestions for that?

We are looking on modifying our done definition for our stories. Right now we consider done when we finish the development, pass through QA and we merge to develop. We would change it to be done only after this feature goes to production and it's merged back to master, but then this ticket would live for quite a while.

I'm wondering if there is no other techniques to do that.

submitted by /u/wanderlustsoul87
[link] [comments]

from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/2DFaRgz

Leave a comment

Design a site like this with WordPress.com
Get started
search previous next tag category expand menu location phone mail time cart zoom edit close