Raw commit

1. git push as usual. [CLI]

Fix an issue withouth review

1. Put in commits "Closes: #234" [CLI]
2. Push [CLI]

Fix an issue with review

1. Go to the issue and click create a branch [UI]
2. and put in commits "Closes: #234" [CLI]
3. Push branch [CLI]
4. In Gitlab, create merge request (optional: put in the tittle WIP to not allow merges) [UI]
5. Review [UI]
6. Apply changes, force push the branch with the fixes and clean history after a possible rebase [CLI]
7. Review the branch itself or the difference between the current one and the prvious one [UI]
8. In Gitlab, accept merge request (tip: mark delete source branch) [UI]

Create new task/issue in a project

1. Go to project [UI]
2. Go to issues [UI]
3. Click new issue [UI]

Managing issues

• Select labels to give importance (critical, crash, minor, enhancement) [UI]
• Select milestones for mark task to be done for a specific version [UI]

• Use the Board to do complex task management [UI]

• Use cross-mention issues for dependent issues. For example, an issue can have a comment with a list of blockers, then when one is closed it will update its visualization with a (closed) label to its side. Then when all of them are closed, you can close the tracker issue.Example issue. [UI]

• Mark as duplicate with the "duplicate" label and mention the #issue.

  Example issue and how it looks in the lists of issues. [UI]

• To move issue to a different project go to "edit" and "move to a project" [UI]
• To mark issue as visible only for developers or confidential, use the checkbox "This issue is confidential" [UI]

Create branch

1. Go to project [UI]
2. Click "create branch" [UI]

CLI management of issues

You can use https://github.com/NARKOZ/gitlab/ [CLI]

Releases

(Initially you would use the current ftpadmin stuff, this is just as future possiblity) https://docs.gitlab.com/ce/workflow/releases.html

1. Click any tag [UI]
2. Add a "note" to it that can be the changes, and it will become a release [UI]