... | ... | @@ -21,9 +21,10 @@ We first give a quick intro to the philosophy of this approach and then show a s |
|
|
`issue` -> `merge-request` -> `do-your-work` -> `mark-as-ready` -> `merge-to-dev` -> `merge-to-master`
|
|
|
|
|
|
## Interpretation:
|
|
|
* `Issue`: You want to create a new research topic or have found a typo. Draw your ticket (`Issue`)
|
|
|
* `merge-request`: Create the framework for offering your solution to the administrators, so they can integrate your contribution on the `dev`elopment branch (quality assurance of content)
|
|
|
* `merge to master`: If the first step of quality assurance was passed, the stability of the webpage is assessed before final publication on the web (quality assurance of webpage logic)
|
|
|
* `Issue`: You want to create a new research topic or have found a typo. Draw your ticket.(`Issue`)
|
|
|
* `merge-request`: create the framework for offering your solution to the administrators.
|
|
|
* `merge-to-dev`: via the `merge-request` so they can check your offering and integrate your contribution in the `dev` branch (**quality assurance of content**).
|
|
|
* `merge to master`: if the first step of quality assurance was passed, the stability of the webpage is assessed before final publication on the web (**quality assurance of web page logic**)
|
|
|
|
|
|
## Step-by-step Tutorial
|
|
|
|
... | ... | |