GitLabs how to

gitlabs1

# GitLabs tricks and How-to 
While reviewing the commit branch you can add specific comments directly to the spot in the code that will flow back to the developer
Each project has a namespace and then a hierachical view of projects - think of the bame space as a group of many projects
Projects come with several tools:
 - Repository for your code
 - Issues
 - Labels
 - Milestones
 - Wiki
 - Merge Requests
As you are creating an issue in GitLabs there is a nice trick to create tasks.  In the Issue description simply use the following syntax "- [ ] my first task is..."
For an Issue us the weight to identify the amount of work required to close the issue
Issues get assigned a milestone and each milestone view has a simple KANBAN board view to track status
When adding files to a repository thru the GitLab GIU:
- The default is the master branch
- When you change the branch name the system automatically creates the new branch and creates a merge request as soon as you click "commit"
- Within the merge request you can reference comments to other user by using the syntax "@username"
- You can connect the comment to any issue by typing "#" and Gitlabs will pop-up a list of issues to choose from (that are within the project)
While in GitLabs the "?" key will bring up all keyboard shortcuts
Once a merge request is completed the issue is automatically closed as well
Think of milestones in Gitlab as a release - so all issues and feature requests for that release should be attached to the same milestone
Milestone progress is based upon the issues open and closed and cannot be manually adjusted