-
-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch from git-flow to a simple git branching model #58
Comments
Force pushing on master is not mandatory. For forks, it is not a real issue since patchs should still apply. The issue is with PRs as you cannot change the target branch. Anyway, I appreciate this. |
I don't have any strong feeling about this, so go ahead :) . |
To simplify branching model, here is what I did:
By doing so, all PR have been closed.
I hope this will not be too painful, but it had to be done. |
I've kind of lost interest in #52 - but if anyone is interested in picking up where I left off they're more than welcome :) And I'll be happy to answer any questions they might have. |
Historically at TailorDev we used to be git-flow people. This is why you will find multiple branches in this repository, e.g.
master
,develop
, and feature branches (feature/foo
). As previously mentioned by @willdurand and after a few weeks working with a simple git branching model, I think we need to clean up this repository and only keep themaster
branch. Every feature or hotfix will be developed in a feature branch and merged to master. All tags should point tomaster
commits.If we do so, this will have consequences for people having forked this repository since we will force push master and remove develop.
Are you ready for this?
The text was updated successfully, but these errors were encountered: