We use GitHub as our primary code repository for our own projects and recommended platform for our clients. We are also migrating away from our current project management and tracking tools to leverage GitHub Projects and Issues for all of our roadmap and project planning tools. We have adopted Wiki for documentation and ensured that all of our tooling is repo based for versioning and portability if GitHub ever ceases to be amazing for us.
Pros
Repository Management
Project Management
Issue Tracking
Users and Roles
Cons
Granular time tracking for issues/projects
Easier Integration into other platforms like Slack (while the connector exists - it is very basic)
Better notifications control around CICD
Likelihood to Recommend
GitHub does repo management really well. The granular and team based user access is very helpful and provides a robust security layer we need without a lot of thought. The project management tools are starting to be really strong with great views for planning needs. Integration into communication tools like slack or teams could be stronger
We use GitHub for the code repository. For all the version tracking, collaborating with multiple developer. We also use GitHub co piolet for development. Different version tracking is really helpful when it comes to the back tracking, also bug fixing. We can see where it is changed, who changed, based on the commit message we can say why it was done. Copilot gives a whole new area to play with. so much possibilities.
Pros
Collaboration with multiple developers. This is very good. either we can work on same branch, or we can work on different branches, then merge to the one main branch, so that all the codes are available.
Cherry picking is very nice, you want only one commit moved to a different branch? you don't have to merge it with complete branch, just one commit you can move.
Labelling is a wonderful feature, it helps to identify which branch is critical, what to touch, what shouldn't be touched.
Cons
Copilot plugin in visual studio seems to have some issues, it goes offline sometimes, this need to be improved.
Code review can be improved, merging on the page it self not that feasible, we have to resolve it offline then push it sometimes. Auto merge sometimes loses changes if complex.
CI/CD configuration is kind of messy, it is hard to maintain if we have to make continues changes to the file.
Likelihood to Recommend
Other that some minor improvement as I mentioned in the previous question, GitHub is a great tool which can be used to transcend your development + code maintenances good experience. It is easy to back track through the changes since the revisions are available. Also we can see what are the available branches, how many I created etc. This also helps to get a overall idea what is going on.
VU
Verified User
Professional in Information Technology (Information Technology & Services company, 201-500 employees)
We use GitHub to manage all of the repos at our organization. We have teams of developers and also take advantage of the AI offerings available. In addition we leverage GitHub actions for deployment and wikis for documentation.
Pros
Intuitive interface for managing pull request and code reviews
Integration with AI tools make GitHub ideal for any organization
GitHub's enterprise level security make it a top notch solution for any Enterprise
Cons
GitHub could use a tool outside of enterprise level to allow merging two organizations together into a single organization
Would be nice to have display names that are separate from GitHub url so we can change or update repos without changing url
Being able to merge in 1 direction instead of a bi-directional merge would reduce headaches in some areas
Would love to see some built in templates for setting up new repos preconfigured with set settings and permissions
Likelihood to Recommend
GitHub is the premier service with the most cutting edge features for anyone that needs version control. It's a superior product to its competitors and easier to use. It's integration with both private and public community makes it a one stop shop solution for any developer. It's team management, security and automation integrations with AI are second to none.
At Qualtrics, GitHub is a core part of our product, support and engineering workflow. It helps us support everything from day-to-day development to deployment, compliance and tracking issues and features. We use it primarily for source control and collaboration across teams, allowing developers to manage code changes, conduct peer reviews, and maintain quality. It also supports issue tracking and documentation, often working alongside tools like Jira, Notion,…to align technical work with broader product goals.
Pros
Integration with other products
Issue and bug tracking
Labelling
Cons
Community Management
Public upvoting and idea generation
Likelihood to Recommend
I’ve worked with Github my entire career and view it as an essential part. As a Product manager it allows me to keep track of my features, epics, issues and QA. It is easy to set up and integrate with tools such as intercom or notion.
We use GitHub for code management, collaboration, project management, and automation.
Pros
Pull request and code review.
Github actions for CI/CD.
Branch protection.
Cons
Complex permission management for large organizations.
Limited advanced search.
Github actions limitations for complex workflows.
Likelihood to Recommend
It is well-suited for collaborative development of Dockerized web apps. Very useful for managing open source contributions. Not much suited for managing large-scale enterprise permissions.
At our organization, GitHub is used as a central platform for source code management, version control and collaboration across Dev and QA teams.
Pros
Pull request workflow and code review
Integration with CI/CD
Issue tracking
Cons
Limited built in test reporting in GitHub actions
Project management features are basic
Likelihood to Recommend
1) It is very well suited for CI/CD for automation testing. GitHub actions enable seamless integration. 2) Version control for agile development. Features like branching, pull request and protected main branch are crucial.
First of all we use GitHub as our primary code hosting platform with git. Using GitHub allows developers to make fast and accurate code reviews with Pull Requests. Another feature we really like on GitHub is the CI/CD automation with GitHub actions. It's so easy to connect your code to any 3rd party tool out there. This saves us so many time... Finally, we use GitHhub as a documentation tool through Markdown files. The docs stay together with code and this is always an advantage.
Pros
Code reviews
Collaboration and issues
Integration with 3rd party services
Open source contribution
Cons
Pricing model (currenty, it is too strict and not flexible)
Custom themes (eg a more wide main area)
Likelihood to Recommend
GitHub is the No1 solution for git hosting, Code reviews, online Collaboration (especially on Open Source projects). The integrations with 3rd party services are also a big advantage. In fact, GitHub can be used as a 360 tool to host, manage, test, deploy and collaborate over code.
On the other hand, GitHub may be an overkill if you are a single developer (so there is no need for collaboration) or if you are working with too many binaries.
VU
Verified User
Engineer in Information Technology (Marketing & Advertising company, 51-200 employees)
Github is our main code repository, version control, and build-integration platform. Github triggers a cloud build, and gives us deployable software.
Pros
Cloud-build integration
Version control
Vulnerability scanning via dependabot
Jira integrations
Cons
The handling of merge-conflicts directly via Github web is difficult
The PullRequest code review tool is frequently troublesome in how it displays the diff between source and changed code.
Likelihood to Recommend
Github can be deeply integrated into a production environment, with build triggers launching a cloudbuild, which delivers deployable code. Multiple active users within a project with overlapping changes are difficult to manage, but definitely doable.
VU
Verified User
Engineer in Information Technology (Marketing & Advertising company, 501-1000 employees)
Every day, we use GitHub for end-to-end SDLC, including project management, codebase CI/CD, and package management, among other things. The branch protection policy has no impact on the production codebase. We handle our automation and deployments with the help of GitHub Actions.
Pros
GitHub Action for your automation, build, test and deployment any platform and any languages
GitHub help store our artifacts and dependency with in Github using GitHub packages
You can integrate with the other third party applications like jira, Azure DevOps etc..
GitHub helps to integrate Development IDE like Visual studio, Eclipse, and jet brain ides etc..
Cons
issues and projects they have to improve little more functionality like conditions for the particular issues or labels
issues create, update, delete options for respective teams or user
in developer workflow mandatory for issues or work-item functionality
Likelihood to Recommend
With GitHub, you can integrate other third-party applications for project management. You can also scan your source code to find vulnerabilities and hardcoded tokens.
VU
Verified User
Consultant in Information Technology (Information Technology & Services company, 201-500 employees)
