Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

[doc] Added our git-flow init settings

  • Loading branch information...
commit 7142e318fcbae4089cd3967731ee26498490f436 1 parent 7ba4f55
@adamretter adamretter authored
Showing with 25 additions and 0 deletions.
  1. +25 −0 README.md
View
25 README.md
@@ -78,4 +78,29 @@ Although the following are taken from our [Developer Manifesto](http://www.exist
- Make sure the approriate licence header appears at the top of your source code file. We use [LGPL v2.1](http://opensource.org/licenses/LGPL-2.1 "The GNU Lesser General Public License, version 2.1") for eXist and *strongly* encourage that, but ultimately any compatible [OSI approved license](http://opensource.org/licenses "Open Source Licenses") without further restrictions may be used.
- Run the full eXist test suite. We do not accept code that causes regressions.
+Our git-flow init settings
+--------------------------
+When we started working with the eXist repo we needed to configure it for GitFlow by running:
+
+```bash
+$ git flow init
+
+Which branch should be used for bringing forth production releases?
+ - master
+Branch name for production releases: [master]
+Branch name for "next release" development: [develop]
+
+How to name your supporting branch prefixes?
+Feature branches? [feature/]
+Release branches? [release/]
+Hotfix branches? [hotfix/]
+Support branches? [support/]
+Version tag prefix? [] eXist-
+```
+
+You can then see that a new 'develop' branch was created and you were switched to it:
+```bash
+$ git status
+# On branch develop
+```
Please sign in to comment.
Something went wrong with that request. Please try again.