Improved Docs

README.md

@@ -6,9 +6,12 @@ scopesessions.org
 * 1.0.0
 * [Learn Markdown](https://bitbucket.org/tutorials/markdowndemo)
 
-**NOTE:** There are two branches:
+### Important development information
-* dev: development branch, merge to master when production-ready
+
-* master: production code, always keep functional and error-free
+There are two branches:
+
+* **dev**: development branch, merge to master when production-ready
+* **master**: production code, always keep functional and error-free. Due to the action of .git/hooks/pre-push it is not possible to push directly into master. Code changes needs to be integrated in master only by merging dev. This way we ensure dev is always in front of master branch. Just experimenting a bit about code versioning mechanisms....
 
 ### Development
 
@@ -25,13 +28,6 @@ bower install
 ```
 jekyll serve
 ```
-* If changes in dev or other branch want to be published, first they need to be merged with on master branch
-```
-git checkout master
-git merge dev
-git commit -m "MESSAGE"
-git push
-```
 
 ### Deployment
 
@@ -39,6 +35,19 @@ git push
 ```
 jekyll build
 ```
+* Commit/Push changes to dev or other branch.
+```
+git add --all .
+git commit -m "Changed this and that"
+git push
+```
+* If changes in dev or other branch want to be published, first they need to be merged with on master branch
+```
+git checkout master
+git merge dev
+git commit -m "Merged master and dev"
+git push
+```
 * SSH into scopesessions.org and pull the changes from master
 ```
 cd /var/www/vhosts/scopesessions.org