Closed Beanow closed 9 years ago
That is a great idea. I will see about implementing a development branch.
Ok I have a simple version of this built up. Think it will work?
Not quite, only master and develop are permanently present. The others are temporary when you need them. For example: release/1.1.0, hotfix/1.0.3, feature/new-shortcuts
Ahh I see. That makes sense.
-----Original Message----- From: "Robin van Boven" notifications@github.com Sent: 2/21/2015 1:46 PM To: "jake-phy/WindowIconList" WindowIconList@noreply.github.com Cc: "jake-phy" jake.phy@gmail.com Subject: Re: [WindowIconList] Use a branching model for stability (#66)
Not quite, only master and develop are permanently present. The others are temporary when you need them. For example: release/1.1.0, hotfix/1.0.3, feature/new-shortcuts — Reply to this email directly or view it on GitHub.
Seems implemented like this.
I would like to make some small modifications to the most recent release, I would need to revert my working tree to your release commit manually. Perhaps you could consider git flow.