You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/development.rst
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -87,13 +87,15 @@ It is highly recommended to use the `git flow <http://github.com/nvie/gitflow>`_
87
87
* clone your fork ``git clone [email protected]:username/django-filer.git``
88
88
* ``cd django-filer``
89
89
* initialize git flow: ``git flow init`` (choose all the defaults)
90
-
* ``git flow feature start my_feature_name`` creates a new branch called ``feature/my_feature_name`` based on ``develop``
90
+
* ``git flow feature start my_feature_name`` creates a new branch called ``feature/my_feature_name`` based on ``master``
91
91
* ...code... ...code... ..commit.. ..commit..
92
92
* ``git flow feature publish`` creates a new branch remotely and pushes your changes
93
-
* navigate to the feature branch on github and create a pull request to the ``develop`` branch on ``divio/django-filer``
94
-
* after reviewing the changes may be merged into ``develop`` and then eventually into ``master`` for the release.
93
+
* navigate to the feature branch on github and create a pull request to the ``master`` branch on ``divio/django-filer``
94
+
* after reviewing the changes may be merged into ``master`` for the release.
95
95
96
-
If the feature branch is long running, it is good practice to merge in the current state of the ``develop`` branch into the feature branch sometimes. This keeps the feature branch up to date and reduces the likeliness of merge conflicts once it is merged back into develop.
96
+
If the feature branch is long running, it is good practice to merge in the current state of the ``master`` branch into
97
+
the feature branch sometimes. This keeps the feature branch up to date and reduces the likeliness of merge conflicts
0 commit comments