#1 most frequent
United States of America
28.8%91,648 installations of 317,777
What is GitHub?
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
Categories & Use Cases
Videos
Top Performing Features
Branching and Merging
Allows users to create separate branches to work on specific features or fixes and merge them back into the main codebase when ready.
Category average: 9
Pull Requests
Provides a mechanism for developers to request code reviews, discuss changes, and merge code into the main branch after approval.
Category average: 9
Branch Protection
Prevents accidental or unauthorized changes to critical branches by restricting direct commits and enforcing code review processes before merging.
Category average: 8.4
Areas for Improvement
Automated Testing Integration
Integrates with continuous integration tools to automatically run tests on code changes, ensuring that new code does not introduce errors or bugs.
Category average: 6.8
Version Control Collaboration Tools
Facilitates collaboration among team members by enabling them to work on the same codebase concurrently, resolve conflicts, and review each other's changes.
Category average: 8.6
Issue Tracking Integration
Integrates with issue tracking systems to link code changes to specific issues or tasks, providing traceability and context for changes made.
Category average: 6.8
Who Buys & Uses GitHub
#2 most frequent
Japan
22.1%70,229 installations of 317,777
#3 most frequent
India
5.4%17,049 installations of 317,777
Pros
- Improved code quality
- Enhanced team collaboration
- Streamlined development processes
Cons
- Basic project management capabilities
- Challenging permission management in complex organizations
GitHub is the game changer for excellence
Use Cases and Deployment Scope
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
Return on Investment
- GitHub helps my team be efficient in project management and every day tasks
- Time Tracking could be integrated to provide tighter coupling for business planning
- The notifications could be more controlled
Usability
Other Software Used
Toggle Global
GitHub Review
Use Cases and Deployment Scope
GitHub is used on different levels in our organisation. From creating and maintaining a pipeline to having version control of internal products that are developed. Maintenance of data products is made easy using this because one can revert back to the old version in case there's a break in the pipeline and so on.
Pros
- Version Control
- Code Maintenance
- Code Storage
Cons
- Better Interface
- Easier Commands
- Larger File Upload Function
Return on Investment
- Increasing Productivity
- Better Management
- Easy Navigation
Usability
My Honest Review On GitHub
Use Cases and Deployment Scope
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.
Return on Investment
- As a developer it only helped me, no negative impact. If we need some for the development back tracking it is there.
- Branching and merging is a wonderful feature, this will give you a great positive impact in your organization, since developers can work there own without dependency then merge there code as needed.
- Pull request and review are very great, this will give the efficiency of the developer.
Usability
Alternatives Considered
GitLab and Mercurial
Other Software Used
GitLab, Mercurial, Atlassian Bitbucket
GitHub is the ideal tool for managing version control at any organization
Use Cases and Deployment Scope
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
Return on Investment
- It's allowed us to scale our team in ways that aren't possible without efficient code management
- We've reduced errors and conflicts by the tools provided to make merging, reviewing code, and managing conflicts that are built in
- Onboarding time is reduced since most developers are familiar with the platform.
Usability
Alternatives Considered
Atlassian Bitbucket, GitLab and Beanstalk
Other Software Used
Beanstalk, Atlassian Bitbucket, GitLab
GItHub for secure and scalable software development
Use Cases and Deployment Scope
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
Return on Investment
- Improved code quality and reduced defects
- Increased developer and QA productivity
Usability
Alternatives Considered
GitLab
Other Software Used
Microsoft Visual Studio Code, Postman, Atlassian Jira