GitHub makes code collaboration simple with an intuitive UI, reliable performance, seamless integrations, and useful AI features like Copilot. It helps keep projects organized and improves development efficiency for both individuals and teams. Review collected by and hosted on G2.com.

While GitHub is feature-rich, some advanced capabilities can be difficult for new users to learn. The pricing for certain enterprise features may be a challenge for smaller teams, and navigating permissions or complex workflows can sometimes feel overwhelming. Additionally, support response times can vary depending on the plan. Review collected by and hosted on G2.com.

Earlier, we used TFS to store our source code, but one limitation was that only one user could make changes to a particular object at a time. With GitHub, our whole team can work on the same object in parallel, with different developers making changes and then merging them smoothly.

For me, the biggest advantage of GitHub is the CI/CD pipelines we built using GitHub Actions. This keeps us deployment-ready as soon as development is ready—once we push to QA or UAT, and then to PROD, the deployment is completed almost immediately. Review collected by and hosted on G2.com.

Since we’re a Data Engineering team that works directly with database objects, GitHub doesn’t natively support versioning those objects unless we rely on third-party tools like Flyway to store the source code and manage deployments. Review collected by and hosted on G2.com.

I use GitHub for saving my college projects, tracking my code changes, and participating in open source contributions. GitHub helps me save my code versions, and if new changes break my functionality, I can revert to my previous version easily. I like the profile badges and the readme.md file, where developers can showcase their profiles. The badges we get are kinda fun, and it's like a badge of honor when we achieve something. The readme.md file is shown on our profile, where we can showcase our tech stack and stuff, and it looks good. It was easy to set up GitHub; I just followed a tutorial. I'd totally recommend GitHub to a friend or colleague, 10/10. Review collected by and hosted on G2.com.

When I push code, I often get merge conflicts, and I believe this could be simplified because sometimes it is confusing. It could be merge conflict and pulling code from origin. Review collected by and hosted on G2.com.

The best thing about GitHub for me is the pull request and code review system. My team works on the same codebase every day, so it's much easier to review changes before merging them. I also like how easy it is to compare branches and view code differences. It has made collaboration smoother and helped us catch issues earlier. Review collected by and hosted on G2.com.

One thing I don't like about GitHub is that managing permissions can become confusing, especially when working on larger team projects. Sometimes it takes time to figure out why someone doesn't have access to a repository or branch. I also get a lot of notifications when working on multiple repositories, so it's easy to miss important updates or comments Review collected by and hosted on G2.com.

For my company, GitHub is very important. We are currently a web- and physical office-based taxi and travels company, but we are expanding to a mobile platform. We use GitHub for our backend code and then integrate it with Render. We also publish our websites there for testing.

The most important part for us is GitHub Actions. Every time we edit the code, it automatically pushes and redeploys to Render. The webhook is also helpful, because we don’t need to push manually. During development, in a single day we may need to update code many times, so this saves my team effort and time. Branch protection is also good.

In development we add many features, like a bid system, so with new branches we can manage everything properly. We don’t need to make multiple repos for the same code. Pull requests are also very important because they allow my team’s senior engineers to review the changes from juniors before deployment, so it doesn’t cause us to repeat mistakes.

We also use GitHub Copilot, and it is very good and intelligent for coding; in my opinion it’s one of the best. The Actions tab also shows clearly if there is any issue in the code during deployment, and GitHub environment security is easy to manage. However, it is slightly deep if we want to change something: we first go to Settings, then Secrets, then Actions. I think it should be more direct. The suggested changes feature is also good. Review collected by and hosted on G2.com.

Well, there are some big problems, especially with notifications. It’s natural that when many people are working and there are lots of updates, the notification section can become a real issue. Many times, important notifications get buried under simple ones like code push, etc., and we face this problem often. It’s good that it notifies us, and it also alerts us when there’s a critical bug in the code, but code push notifications can still bury the bug notifications.

Also, currently there is a delay in actions. When we deploy, many times it takes longer and feels slow. Previously it was fast, but in the last 2 to 3 months we’ve seen it taking more time and slowing down. Even when we publish the page, it takes time.

On the other hand, the GitHub remote repo is good for pushing files from a local PC to the repo. But when we try to upload files manually, we can only upload 100 files at a time. It’s normal to have more than 100 files in one go, even for backend work, like a ride-hailing backend.

Overall, I don’t find any major issue, and according to me GitHub is well developed in terms of tech and features, and it feels honest for most users. Still, some normal things are bad. They should give simple options like stopping push/update notifications, and make deployments fast again. Also, there are many new features in the UI, which is good, but it makes it harder to find the settings and features that I want. With time I can understand it as an engineer, but not as a founder. Review collected by and hosted on G2.com.

It is free to use, it has a history so I rely on it (things are not changing over night). You can have a public or a private repo for your project. You can easily run workflows free (so if one considers a VPS this is a better option for smaller scripts). Git is simple and easy to learn - you have commit history. There is an option to report issues and send pull requests. UI is simple and easy to learn. I never needed to contact their support as everything works well. There are no issues with the performance. The page is down from time to time but it is not a big deal. I also recently discovered that I can have code spaces that will allow me to affect my backend that saves a lot of time and money. I adore the fact that copilot (AI bot) is helping me some of my issues within the pull requests. Review collected by and hosted on G2.com.

It was quite new to me (and a bit frustrating) that you cannot add a folder and see it in the structure (but this is how it works). Besides that I do not have any issues with GitHub. Review collected by and hosted on G2.com.

What I like most about GitHub as it is one of the best platforms for open source professionals. It keeps all my code in one place, tracks every change, makes collaboration easy, lets me showcase projects through public repositories and even offers free hosting via GitHub Pages. Review collected by and hosted on G2.com.

No big dislikes, but sometimes when two people make changes to the same file it creates conflicts which can be a bit confusing to resolve Review collected by and hosted on G2.com.

I like the simplicity of GitHub because it is so simple to manage projects. Creating a new repository to show my project or collaborating with my friends is really straightforward. The collaborating part is what I love the most. The interaction between GitHub and Visual Studio Code is very nice. I just need to type two or three commands in the terminal and my project gets pushed to GitHub. Also, when there's five of us working on one project, the interaction between devices is very smooth. Review collected by and hosted on G2.com.

So sometimes I found it too difficult. Like, if a user is new to GitHub, then he might or she might feel your complexity there. It means it is not so much user-friendly at the beginning. But, as soon as you start using it on an everyday basis, it works well. So, likewise, I said that the initial setup for GitHub was a bit difficult for me. Initially, it was more on the complex side for the user. It is not much as user-friendly like it should be. But, as soon as I started using it on an everyday basis, I got along with it, and now I find it very user-friendly. But initially, it was a bit on the tougher side. Review collected by and hosted on G2.com.

I love GitHub for its powerful platform that makes managing code and collaboration with developers efficient. Its version control and teamwork features are seamless, making it easy to manage code, track changes, and collaborate effectively. The use of branches and pull requests allows multiple developers to work on the same project without conflicts, making it simple to review code, suggest improvements, and merge changes safely. I also appreciate the integration with tools like VS Code, Docker, and AWS, which streamlines coding, testing, and deployment workflows. Switching to GitHub from another platform has improved our overall development workflow and made team coordination much smoother. Review collected by and hosted on G2.com.

GitHub can sometimes feel complex for beginners, especially when learning Git commands and workflows. The interface for managing issues and projects can also feel overwhelming at times. Review collected by and hosted on G2.com.

The ease of use of GitHub comes from the fact that it works really well when using teams and version control. It is also great how easy it is to manage your repositories and keep track of the changes through pull requests. It is also nice how you get integration with CD tools such as GitHub Actions and how that automates the entire process. Review collected by and hosted on G2.com.

This is very much cluttered as far as the user interface is concerned. Managing multiple branches becomes very difficult, not to mention merging of files. Merging conflicts tend to be quite a task for beginners, especially for new team members. Review collected by and hosted on G2.com.