Commit f09fbdf1 authored by Rami Alshafi's avatar Rami Alshafi

Update getting_started.md

parent 36da52c5
......@@ -64,17 +64,18 @@ Merge conflicts will be highlighted in the merge request along with the result o
To create a new issue, click on the "issues" option in the main menu on the left of the project page and click on the "New issue" green button.
![New Issue button](/assets/NewIssueButton.png)
The new issue form will open up, fill it up with the proper title and description and assign it to whomever is responsible. You can also associate your new issue with the proper milestones and labels if that makes sense for your issue along with a due date. The "Submit issue" button will light up green and becomes clickable. Click it to create the issue.
![Issue Form](/assets/NewIssueForm.png)
![Issue Form](/assets/NewIssueForm.PNG)
Once the issue is created, your teammate with the proper permissions will be able to vote it up or down, comment or start a discussion thread about it. Whoever is responsible for fixing the issue can create a new merge request from your issue and the issue will be automatically updated as the merge request matures.
![Issue Page](/assets/issuePage.png)
![Issue Page](/assets/issuePage.PNG)
### Orgnize Issues
Issues can be organized into boards of a project and each board can have multiple lists of issues. Each board could be specific to a milestone or to a specific team and the lists within these boards could be a done pile for example or a backlog pile or Work-In_Progress (WIP) pile.
## Continuous Integration
Continuous Integration is one of the main advantages of Gitlab! In fact, it was rated as the best by the [Forrester CI Wave ™](https://about.gitlab.com/resources/forrester-wave-cloudnative-ci/) report.
To see the pipelines and the jobs of a project, click on the CI/CD option from the project menu then click on pipelines.You should be able to see all the historical pipelines.
![pipelines](/assets/pipelines.png)
![pipelines](/assets/pipelines.PNG)
From there, you can click on the jobs themselves and see the logs and the console.
![Job consol](/assets/job_consol.png)
![Job consol](/assets/job_consol.PNG)
## Recommended Workflow
Gitlab workflow is highly flexable there are many possible workflows that can suit the needs of many teams. However, with flexability, comes complexity. the Gitlab recommended workflow is the following
* start an issue
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment