GitLab

This is one of the key use case for using this products and make life easier for our employees

Collaboration is easier when using Gitlab. Developers can push the code changes in the feature branch by adding commits. Those code changes can be reviewed using the Changes tab of the merge request. Developers can put the comments when doing the peer code review. Then those comments can be resolved by adding new commits. That's how collaboration is easy when using Gitlab because it provides all the necessary features which enriches the user experience.

Yes, it made managing code and assets related to the code easy.

It made collaboration incredibly easier! Gitlab serves as the central nerve for nearly all of our projects, where we store code, documentation, configuration for every project of the entire company. Accessing and working on code and documents at the same time, from the office or from home, Gitlab is one of the best collaboration tools, and it's main power is in collecting all the different features of a softwer writing process to the same place.

Yes, it certainly makes. Currently, I'm using Gitlab to host the source code for one of my clients and it certainly makes the code easy to collaborate. We use the full feature set: code hosting, CI, pull requests, etc. The interface is very clean and makes everything obvious for all developers. The fact that we can configure the CI via yml file in the source code is another plus.

Merge Requests and Issues are the main GitLab collaboration fearures used by the teams I work with.
The team uses branching to work on new application features and then submits merge requests to bring the code into the main branch of the repository. Most of our repositories have protected main branches so communication around incoming code is a must. The merge request console really let's us focus on the code that's coming in and discus anything that might need closer review. All of this discussion happens right in the application so there's a history of the discourse. Along with that, if anything needs to be changed, devs can make the changes right i the web UI and commit the changes back into the merge request.

With Issues, the developers tie feedback from stakeholders directly to lines of code. This helps them track bugs from open to closure. Assigning someone to an issue is helpful so the team knows who is working on which issue.

Like any other git/source control service, Gitlab has collaborative code review tools that help communicate requested changes and comments to pull requests. It's feature set is comparable to Github. It's probably not as full featured as Github as a comparison, but it does what it needs and provides enough tools for any development team to collaborate using it.

Gitlab makes team collaboration a breeze. Literally a life saver keeping me from having to keep track of all these different tools for artifact storage, pipelines, code management, issue tracking, etc. Doing it all in Gitlab just makes things WORK. It also helps standardize platforms so you do not have teams using 20 different tools to accomplish the same goal.

Gitlab has allowed my team to be able to review code, as well as give approval for code roll outs. This has allowed us to make sure that our code has less errors as well as track changes that are made through the software's life cycle.

Yes we use gitlab to store more than 10 different code projects. Thanks to CI we enabled automations to connect Gitlab to third party services like Slack and really helped team collaborating.