Merge branch 'dev'
Conflicts: README.md
This commit is contained in:
commit
e964b244b3
1 changed files with 4 additions and 2 deletions
|
|
@ -9,8 +9,10 @@ scopesessions.org
|
||||||
### Important development information
|
### Important development information
|
||||||
|
|
||||||
There are two branches:
|
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....
|
* **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
|
### Development
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue