 הי, מי name איזה יציגן ברור, טכניקל מרקטינג מיננגר עד גיטלאב. In this video, I will focus on the value you can get from the combination of SCM, CI, and code review delivered as a single application. SCM, CI, CD, and code review are key tools developers use daily to develop applications. In many organizations, those tools come from different vendors, and they use integrations and plugins to make them work together. While those integration usually works, it is not the ideal way to deliver software today, as you will need to switch between tools, make multiple logins, and spend more time to get what you need. This makes it harder to communicate and collaborate. In addition, you need to maintain multiple tools, plugins, and integrations. GitLab solves this challenge as it has a leading SCM and leading CI, CD, both in one application out of the box. In this demo, I will walk you through the seamless flow developers experiencing with GitLab. Once the developer pushes his code to the server, he can immediately see his branches, commits, and the pipeline status for each commit. The developer goal is to push his code to the master branch as soon as possible. Merging code to the master branch is done via the quality and compliance gate. In GitLab, we call this gate a merge request. In this gate, developers request to merge their feature branches into the master branch. To pass this step successfully, several things should be reviewed. They will need to ensure the new code doesn't break anything, doesn't introduce new bugs or any security or compliance risks, and this is why the CI pipeline runs many tests and scans. It would be helpful if reports from all tests and scans will be accessible to developers in one place so they will be able to get all the info they need easily. In GitLab, the merge request is the single source of truth for that. Information such as pipeline status, test results, security, and compliance scans will appear in the merge request. A review app is a live instance made of the developer's branch. This helps to visually review the proposed change. Once they checked all tests and scans, the next step will be a code review. They can open the code review module by clicking the changes tab. This module enables an efficient review process. And this leads me to the pipeline management module. From the merge request, developers can open the pipelines related to their merge request by clicking this link. This saves time as they don't have to context-witch to another application. The other way back also works. From the pipeline graph, they can click to the commit that triggered it or to the merge request that it is related to it. Having the info all together makes it easy to get an overall analysis of how we are doing. The Value Stream Analytics module shows how much time it took to complete each stage of the development lifecycle. With this analytics, you can identify the slowest stages, improve them, and shorten your time to value. Remember, it sounds obvious, but having everything you need available at all times makes for more efficient work. Stay tuned and see you again at my next demos.