|
|
# Working with Gitlab
|
|
|
|
|
|
There are help pages for every interaction with Gitlab [here](https://gitlab.linguala.com/help) or on the top right where the question mark is.
|
|
|
|
|
|
Devops Lifecycle: https://gitlab.linguala.com/help#the-entire-devops-lifecycle
|
|
|
|
|
|
The important bits are: Plan, Create & Verify
|
|
|
|
|
|
|
|
|
## A Brief Overview
|
|
|
1. Create an issue for work that needs to be done
|
|
|
2. Add `To Do` label if you want it done soon
|
|
|
3. Assign to someone, or wait for someone to take it
|
|
|
4. When you start working on it add the `Doing` label to tell others you've started (and remove the `To Do` label - use board view (Issues -> Board) for that)
|
|
|
5. Create a [Merge Request](https://gitlab.linguala.com/help/user/project/merge_requests/creating_merge_requests.md).
|
|
|
> [more about Merge Requests](https://gitlab.linguala.com/help/user/project/merge_requests/getting_started.md#what-you-can-do-with-merge-requests)
|
|
|
6. Create an [associated branch from the merge request page](https://gitlab.linguala.com/help/user/project/repository/web_editor.html#create-a-new-branch-from-an-issue)
|
|
|
7. Do the work on the branch (e.g. `git checkout 1-branchname` for merge request !1)
|
|
|
8. Commit and push the changes
|
|
|
> after pushing your local branch to gitlab's remote branch, the Merge Request will automatically update if the working branch has been created from the web-editor (point 6)
|
|
|
9. When finished, assign the issue to someone for review
|
|
|
> [remove the 'WIP'](https://gitlab.linguala.com/help/user/project/merge_requests/work_in_progress_merge_requests.md#removing-the-work-in-progress-flag-from-a-merge-request) in Merge Request title to signal for the reviewer that it is ready to be reviewed.
|
|
|
10. The issue closes automatically when a merge is complete
|
|
|
11. Try to make sure it is [mergeable](Why-is-my-Merge-Request-not-mergeable%3F) at the time of review. |
|
|
\ No newline at end of file |