GitHub Reviews

“Integrations are great!”

Pros

Working with this version control system has made coding, deployment and repository maintenance much more manageable for our team. It's especially strong when it comes to automating workflows. It also integrates really well with other UI platforms like SourceTree which makes the overall experience more user-friendly.

Cons

Managing permissions and security through access tokens gets complicated. It can also become expensive for larger enterprises. Also some of the more advanced features are a bit harder for new users to get used to.

“Impressive collaboration and code tracking”

Pros

This tool made collaboration and code management much more manageable for our small team. Github's version control tools kept everything organized and helped avoid mix-ups when several people were editing the same files. It was really handy to follow updates, review code changes and manage repositories from one place. The integrations with other tools, along with the automation options, also boosted productivity without needing a big IT setup.

Cons

One area that could be better is that some of the more advanced features take a bit of time for new users to understand. For a small business team without dedicated developers, setting up permissions and workflows came with a slight learning curve.

“made our workflow better”

Pros

Git-based version control works really well here. Branching, merging, pull requests and commit history are handled reliably which makes working with a team feel organized and dependable. The pull request and code review process is also very well designed, with inline comments, suggested edits, required reviewers and status checks that help keep reviews efficient and structured.

Cons

The platform can still feel a bit intimidating for newcomers or people who aren't very technical. And while it has come a long way, the tool still doesn't offer the same level of depth you get from dedicated project management tools like ClickUp or Jira.

“Excellent tool!”

Pros

Working with It has made collaboration and version control much more efficient across development and automation testing projects. The integration with VS Code was a big plus since it made committing, reviewing and managing code a lot more convenient right from the editor. Pairing It with Playwright also helped simplify our test automation workflow, keep test scripts organized and work better with teammates through pull requests and branch management.

Cons

Handling merge conflicts and setting repository permissions sometimes needed extra attention. Also some of the more advanced enterprise features and CI/CD options can get expensive for smaller teams.

“fantastic for code collaboration”

Pros

Github has proven to be a really strong tool for managing code versions. It makes working with others and organizing projects very simple. The interface is clear and it doesn't take long to find your way around.

Cons

At first, it takes a bit of getting used to specially if you've never worked with Git before. The learning curve feels a little steep in the beginning but that settles down pretty quickly.

“Made managing projects easier”

Pros

Being so widely adopted by developers is a big plus and the fact that it's free makes it even better. Working together on projects with multiple people is also very convenient and simple.

Cons

Honestly.. I don't have much negative to say, it works the way I expect it to and all the features I need are there. If I had to point out anything, the menu layout could be a bit simpler since some functions and settings take time to locate.

“powerful AI-driven workflow hub”

Pros

It has become incredibly powerful thanks to how quickly its AI capabilities have advanced. At this point, it does much more than serve as a code repository. It is versatile enough that we've even shifted our entire technical hiring process into it. We use Github repositories alongside Claude Code to assess candidates and keep track of each hiring stage. Having our developers evaluate candidates in the same environment they already use every day is a really smart setup and ends up saving us a lot of time.

Cons

Because the interface is clearly designed with developers in mind, business teams need some onboarding before they feel comfortable using issues, project boards and markdown. Also, the pricing for advanced AI features and Enterprise plans can become expensive pretty quickly especially for bigger teams.

“Git collaboration for the win”

Pros

Having Github Actions built in is a huge win for our workflow. We can automate testing and deployments directly in the platform instead of maintaining a separate CI/CD server. The ecosystem is also incredibly broad, with connections to tools like Slack, Jira and AWS and the large community makes troubleshooting much simpler when issues come up.

Cons

The interface can feel complicated for beginners and some of the more advanced features take time to fully learn and use confidently.

“great automation and integrations”

Pros

Version control with Git is one of the things I appreciate most, along with how well it supports teamwork. Features like pull requests and continuous integration make collaboration between teams much more efficient.

Cons

I feel that the pricing jump to the Enterprise plan is pretty steep for growing teams especially once advanced security features are added. There's also a noticeable learning curve for non-developers since the interface can be intimidating if you're not comfortable with Git terminology. Also, notifications can become overwhelming on busy repositories unless you spend time fine-tuning them.

“Strong version control”

Pros

I'm really impressed with how this software brings version control and collaboration together in such an organized way. It makes tracking changes simple, lets multiple people work on the same project without chaos and keeps the full code history intact. The platform has strong features for both solo developers and teams specially pull requests, issues and branching. the Github Actions feature is another big plus since it cuts down on manual tasks and helps speed up development workflows. Getting started is fairly simple and after learning the basics, it becomes very practical for everyday use. It also runs reliably with very few bugs or disruptions. From a value standpoint, it offers a lot even on the free plan so it works well for small projects as well as bigger teams. Overall, it feels dependable, polished and built with software development collaboration in mind.

Cons

Honestly there are no major downsides in day-to-day use. If I had to point out one small issue, it would be that Git Actions can take a little time to fully understand when setting up more advanced automation especially for more complex workflows. Basic setups are simple but the deeper configurations can involve some trial and error in the beginning.

“Fantastic features”

Pros

It has been really effective for version control and repository management in my workflow. I use it to push projects, keep track of changes and handle branches while working on backend and development tasks. The connection with Visual Studio Code is especially convenient since I can commit and push code straight from the editor without having to jump between different tools. Pull requests, issue tracking and commit history make it much easier to stay organized and collaborate with others efficiently. It is also a strong platform for building a portfolio and sharing projects publicly.

Cons

Getting started with it can be challenging especially for beginners trying to understand branching, merging and conflict resolution. The interface includes a lot of options so it can feel a bit overwhelming at first. On larger projects, setting up repositories and permissions properly can also take some time. There are also moments when merge conflicts need to be resolved manually and that can slow development down.

“Integration and automation tools stand out”

Pros

Version control is one of the biggest strengths here since it makes tracking changes, seeing who updated what and rolling back to earlier versions really simple when needed. The pull request workflow is another standout because it keeps code reviews structured and helps catch issues before anything gets merged which improves overall code quality. Team collaboration also works really well through branches, comments and shared repositories so multiple people can contribute without interfering with the main codebase. Also, the integrations and automation tools are genuinely useful for handling testing, deployment and broader project management all in one place.

Cons

The part that can get confusing is managing permissions and repository settings especially with larger teams where access levels, branch protection rules and admin controls are located in different areas.

“top-tier developer workflow”

Pros

Right from the start, the developer experience feels top-tier. Github Actions makes setting up CI/CD very simple and the pull request interface is still the most effective way to handle code reviews I've used in the industry. It has boosted my day-to-day productivity quite a bit because it connects with nearly all the tools I rely on, including Slack, Jira, my IDEs and Copilot.

Cons

Notifications can get a bit overwhelming on bigger projects if they aren't configured carefully. Github Projects is pleasant to use and offers a really good experience overall but it still needs more development to match the depth of dedicated tools like Jira especially when it comes to supporting more complex agile workflows.

“A great software overall!”

Pros

Among all the CI/CD tools I've used, Git Actions is still the one I'd pick first. It feels fast to get going, performs really well, supports multiple operating systems and even makes self-hosted on-prem runners possible without much setup. A huge part of its strength is the ecosystem... there are thousands of reusable community actions covering almost any scenario which means you almost never need to build things from scratch. That saves a lot of time in daily work. Outside of Actions, the pull request flow is excellent and the collaboration tools especially Issues and Discussions are very practical and thoughtfully built. It is also basically the default platform for open source now.. nearly every important project is on it and free public repositories make it the obvious place for community software. I use it both for personal open source work and in enterprise environments and it fits both use cases very well. Being able to manage public and private repositories in one place instead of juggling separate platforms is a major benefit.

Cons

The notification system is genuinely frustrating for my use case. There are just too many notifications and it becomes very hard to spot the ones that actually matter, like comments on my own issues, review requests or mentions. Because of that, I sometimes miss important updates unless someone points them out directly or I happen to notice them myself.

“perfect for remote teams”

Pros

The collaboration features are excellent and the version control is really strong. It also connects with a wide range of tools which makes the ecosystem feel very complete. Since it's cloud-based, it works especially well for remote teams and distributed workflows.

Cons

Getting started can be challenging for beginners. Git concepts and workflows take a while to fully understand and the initial setup can feel a bit complex.

“fantastic git integration”

Pros

It's an excellent tool that works perfectly with Git and it gives you both a customized terminal interface and a GUI option. Github makes development, code management and team collaboration feel really efficient and pleasant to handle.

Cons

The Actions area could be made more simple so building efficient workflows would be simpler.

“Keeps work organized”

Pros

Keeps my client work organized and much easier to handle. I use it to save and share prototypes, manage version history and show clients exactly how a project has evolved over time. Being able to review changes and quickly roll back when something goes wrong has been incredibly useful. It gives both my clients and me more confidence when we're testing new ideas and making updates.

Cons

One area where it has been frustrating is support. Getting direct help beyond the community isn't very simple since most of the time you're limited to submitting support tickets. Responses can take a while and it often feels difficult to get prompt, personalized assistance when problems come up.

“Github Actions saves time”

Pros

It has been a really strong tool in my daily workflow because it's packed with useful features for version control and team collaboration. The tool helps a lot with fixing bugs or issues and handling merge conflicts directly on the platform without needing to open an IDE. Getting started is quick and simple and Github Actions feature has been especially valuable for cutting down time spent on repetitive work like builds and deployments. Overall, it feels like good value for the money since it brings code management, collaboration and automation together in one place.

Cons

I don't really have any major complaints about it although some of the more advanced features can be a bit confusing at times and that does make it feel less user-friendly in certain situations.

“a reliable management tool”

Pros

Working with Github has been a really positive experience because it's simple to use and since so many people rely on it, there's a huge amount of online help available whenever I get stuck setting something up.

Cons

Switching between repositories can be a bit awkward at times. When you're dealing with multiple organizations, moving from one repo to another doesn't always feel very smooth.

“incredible collaboration and version control”

Pros

This software does a really good job of handling code hosting and version control while also making collaboration with other people and planning software updates much more manageable.

Cons

Something I'd like to see is an option for maintainers to disable the fork button so they can guide contributors toward being added directly to a project instead.