Changes

Page history
Update GitLab MWT authored by Thomas Vierjahn's avatar Thomas Vierjahn
Hide whitespace changes
Inline Side-by-side
GitLab-MWT.md
View page @ cd8b4d8b
...@@ -2,6 +2,17 @@ ...@@ -2,6 +2,17 @@
This is our best guess of good practices to start coding with. This is our best guess of good practices to start coding with.
* [Misc](#misc)
* [Mantras](#mantras)
* [Commit](#commit)
* [Releases, Develop, Master](#releases-develop-master)
* [Milestones](#milestones)
* [Issues](#issues)
* [Feature Branch](#feature-branch)
* [Merge Request](#merge-request)
* [Closing Issues](#closing-issues)
* [Boards](#boards)
## Misc ## Misc
We use a git-flow-based workflow. We use a git-flow-based workflow.
...@@ -137,4 +148,4 @@ Each column has its own label attached. When you flag an issue with that label, ...@@ -137,4 +148,4 @@ Each column has its own label attached. When you flag an issue with that label,
Newly opened issues will always show up in *backlog* and closed ones in *close*, though. Newly opened issues will always show up in *backlog* and closed ones in *close*, though.
You can freely move issues through the pipeline by drag&drop. You can freely move issues through the pipeline by drag&drop.
Please make sure to consistently update issues in oder to preserve a reasonable representation of progress. Moreover, be aware that gitlab tracks the issue life cycle by [cycle analytics](https://about.gitlab.com/features/cycle-analytics/). Please make sure to consistently update issues in oder to preserve a reasonable representation of progress. Moreover, be aware that gitlab tracks the issue life cycle by [cycle analytics](https://about.gitlab.com/features/cycle-analytics/).
Eventually, this feature will help us understand how fast we can realistically work and hence "what we can ultimately afford". Eventually, this feature will help us understand how fast we can realistically work and hence "what we can ultimately afford".
\ No newline at end of file