Some challenges arise when Git is not used correctly, particularly in managing branches. It's easy to get lost, but these challenges can be overcome with proper management. A common advice is maintaining the repository and ensuring developers are in sync with the production branch. Branches should be promptly merged into development to avoid getting lost in many branches.
I believe there is room for improvement in preventing work loss due to conflicts or overwriting. Another area for improvement could be implementing features for automated code verification within Git.
Professor at FESB - Faculty of Electrical Engineering, Mechanical Engineering and Naval Architecture
Real User
Top 5
2023-07-06T09:12:52Z
Jul 6, 2023
The main problem for me is the frequent upgrades in the solution because every other upgrade is a minefield. When you do the upgrade, there is always something that doesn't work. We have to spend days to correct it. Then, we stop all updates, and we do the updates in six months or a year. There is always a problem, especially if you do an update, since after that, some libraries don't work. We then spend a lot of time trying to fix it. Therefore, the frequent updates are really, really terrible. The aforementioned area can be improved.
DevOps Engineer at a tech services company with 51-200 employees
Real User
Top 5
2023-06-06T18:30:00Z
Jun 6, 2023
I don't think it does need any improvement for now since Git is a free, open-source project. To be honest, I didn't even get close to seeing all its current features. So, I can't imagine any new features that I would be able to recommend. If it was possible to pay for a Git solution, I would pay for it. However, it's difficult in my country. So I mainly enjoy the free solution.
The price is an area that needs improvement. The process of raising a pull request could benefit from some improvement. Currently, when a pull request is created in an organization, a branch is also created. However, each pull request must be individualized to a specific branch. If another person raises a pull request under the same ID assigned to the previous person, and both parties modify the tool, their changes will be grouped together in the same request until it is closed, which is an issue. Therefore, it would be beneficial if pull requests were individualized to each user so that any modifications made are attributed to the specific user's pull request.
You have Git Lab as a platform, which is just Git with a web interface. I believe that is already well integrated. More security is always welcome in my opinion.
Head of Emerging Technologies at a construction company with 1,001-5,000 employees
Real User
Top 10
2023-02-13T20:28:06Z
Feb 13, 2023
There is no standard for managing feature branches. While there are branches created, and they can be reviewed before merging, there isn't yet a standardization, which means the team has to follow up. New developers sometimes find it difficult to call a review or create a request. They don't necessarily know what to push or if they should be creating feature branches, etc. The should work to make it simpler to use with more standardization to help new users acclimatize faster.
We have had a mixed reaction to the newly-introduced code pilot. It improved the coding but was also gave too much to the AI and people are concerned that Git Copilot could result in a lot of job losses.
If the file changes are on the same line, we need to resolve a merge conflict manually. Let's say there is a merge conflict on line 50 because we have multiple commits on the same line number. Git could add some artificial intelligence to resolve the conflict automatically. I would also like to see a GUI like Visual Studio Code and Linux has.
Practice Manager at a comms service provider with 10,001+ employees
Real User
2019-09-08T09:50:00Z
Sep 8, 2019
I would like to see an improvement in the way the product owner can review changes and so forth. But I believe there are licensing costs related to that. It would be better to keep everything simple with one standard license fee.
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.
There is nothing that could be improved at this time.
Some challenges arise when Git is not used correctly, particularly in managing branches. It's easy to get lost, but these challenges can be overcome with proper management. A common advice is maintaining the repository and ensuring developers are in sync with the production branch. Branches should be promptly merged into development to avoid getting lost in many branches.
I believe there is room for improvement in preventing work loss due to conflicts or overwriting. Another area for improvement could be implementing features for automated code verification within Git.
I would like to see less updates with the product.
The price could be improved.
The platform could have a feature for monitoring data recovery similar to Azure.
I would like more documentation.
The main problem for me is the frequent upgrades in the solution because every other upgrade is a minefield. When you do the upgrade, there is always something that doesn't work. We have to spend days to correct it. Then, we stop all updates, and we do the updates in six months or a year. There is always a problem, especially if you do an update, since after that, some libraries don't work. We then spend a lot of time trying to fix it. Therefore, the frequent updates are really, really terrible. The aforementioned area can be improved.
I don't think it does need any improvement for now since Git is a free, open-source project. To be honest, I didn't even get close to seeing all its current features. So, I can't imagine any new features that I would be able to recommend. If it was possible to pay for a Git solution, I would pay for it. However, it's difficult in my country. So I mainly enjoy the free solution.
The price is an area that needs improvement. The process of raising a pull request could benefit from some improvement. Currently, when a pull request is created in an organization, a branch is also created. However, each pull request must be individualized to a specific branch. If another person raises a pull request under the same ID assigned to the previous person, and both parties modify the tool, their changes will be grouped together in the same request until it is closed, which is an issue. Therefore, it would be beneficial if pull requests were individualized to each user so that any modifications made are attributed to the specific user's pull request.
There is room for improvement in the pricing model of Git. Maybe providing a cheaper version for individual users.
It should be more user-friendly. Git provides important commands for projects. It's not very user-friendly, but it's okay.
If the solution could provide more language support options such as Korean, it would be helpful.
You have Git Lab as a platform, which is just Git with a web interface. I believe that is already well integrated. More security is always welcome in my opinion.
There is no standard for managing feature branches. While there are branches created, and they can be reviewed before merging, there isn't yet a standardization, which means the team has to follow up. New developers sometimes find it difficult to call a review or create a request. They don't necessarily know what to push or if they should be creating feature branches, etc. The should work to make it simpler to use with more standardization to help new users acclimatize faster.
We have had a mixed reaction to the newly-introduced code pilot. It improved the coding but was also gave too much to the AI and people are concerned that Git Copilot could result in a lot of job losses.
If the file changes are on the same line, we need to resolve a merge conflict manually. Let's say there is a merge conflict on line 50 because we have multiple commits on the same line number. Git could add some artificial intelligence to resolve the conflict automatically. I would also like to see a GUI like Visual Studio Code and Linux has.
Git could improve the merge conflicts. In a future release, the user interface should be easier to use and more intuitive.
We would like to see tutorials added to the product, for new users to follow so that they can optimize their use of the solution.
I would like to see an improvement in the way the product owner can review changes and so forth. But I believe there are licensing costs related to that. It would be better to keep everything simple with one standard license fee.
The GUI needs to be improved.