Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of GitHub, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Starting price (does not include set up fee)
- $4 per month per user
- Tech Details
|Deployment Types||Software as a Service (SaaS), Cloud, or Web-Based|
- Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
- Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
- Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
- Search functionality, have a better way to search for a sample of code
- Code visualization, have a better way to compare diff versions of code in a file
- Customization, have more customization options, such as the ability to create custom workflows and add custom tools and integrations
- Integrated peer reviews allow engineers to collaborate efficiently and ensure the conversation is preserved for historical purposes.
- The rollout of GitHub actions has enabled our teams to reduce dependencies on external CI/CD services and increase engineering by having less systems to utilize/manage.
- When it comes to Compliance and Security, the GitHub Team editions should provide the ability for SSO or the ability to limit invites to approved business domains.
- Cloud-build integration
- Version control
- Vulnerability scanning via dependabot
- Jira integrations
- 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.
- 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..
- 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
- Able to switch back to previous code if error occurs while running present code.
- Enables us to work in a team in an effective manner.
- Allows giving roles and access to specific people assigned.
- We can choose between private and public repository that enhances privacy.
- Deleting a folder is pretty hard in GitHub. It should be made as easy as deleting a file.
- It would be better if the code editing environment has more features like other IDEs.
- GitHub helps my organization to host Source code repository without hassle.
- Dependa Bots and Integrations with third-party apps are great, A lot of options are available.
- GitHub package repository and Container Registry is also very useful.
- Lack of rich CI/CD which is better by all means in GitLab.
- GitHub should focus on CI/CD they are very good at source code repository hosting.
- Dosen't provide [a] self managed offering. We can't download, install, and setup our own GitHub server if we want to use GitHub we can use Github.com only.
- Excellent user interface that allows for quick assessment.
- Seamless integration with local git configuration.
- Fosters involvement with the open-source community.
- Difficult to permanently remove unwanted files.
- Comments are sufficient to count for repository contributions, which is misleading.
- Notifications can be missed.
- As a repository it's great. It houses almost all the open-source applications/code that anyone can fork and play with. A huge collection of sample codes available with problem statements across different domains make Github a one-stop location.
- I use GitHub with Windows and the Git Bash is superb. It [is] a powerful alternative to the Command Prompt and Powershell. Allows me to run shell scripts and UNIX commands inside the terminal [on] a Windows PC.
- GitHub integration with almost all cloud development/deployment platforms is amazing. Deploying a new application in Azure is really smooth. Just link the GitHub repositories and it's good to go. From automatic build to deployment everything is just amazing.
- Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
- Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
- Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
- While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
- When we want to setup an automated deployment pipeline.
- When we need a repository while working on open source projects supported by a huge community.
- If you want to deploy the programs in cloud platforms. Tested on platforms like AWS, Azure, GCP, Heruko.
- When the need is just for version control. GitHub is more than that.
- GitHub has a powerful UI for creating pull requests
- It makes it easy to research and find what code changed and when.
- It is reliable and dependable. I've used it for four years without issue.
- I would like to be able to view commits by user.
- Conflict management could be improved.
- Navigating around a GitHub repo can be a little confusing until you're used to it.
- GitHub is easy to use and handle i.e. not much training you need to be if implemented in project.
- Also merging capability and solving merge conflicts is easy in GitHub.
- GitHub is a costly tool so not every organization can afford the license of it.
- GitHub has security issues because it upload data on cloud which is venerable to attack.
It is very easy to integrate with third parties.
It provides visibility in scrum planning.
it is very much capable of giving the devops pipeline view and understands the overall product need.
the only drawback is the pricing for the license which might not be affordable if you are a small startup. The open source platform makes it vulnerable for the hackers to get into
- GitHub actions easily help manage pipelines of the application and with these, you can do code health checks and deploy to any platform.
- Proper clean and simple project management via issues and boards.
- Analytics of one's contribution over a period of time.
- It has lots of widely popular open source projects.
- The project management could be a bit more robust by proving epics.
- Would be better to be able to merge organization and personal account contribution over the year.
- Actions marketplace could be better by automatically installing them in the specified repo.
- Easy to use
- Distributed development
- Large community
- Open Source
- Continuous integration leads to problems
- Worst team experience at same project
- Nested commands
- Seamless integration with Git. Although you can use Git without using GitHub, the two have become almost synonymous.
- It provides a nice web-based UI for interacting with your central Git repository.
- Facilitates working with multiple branches, forks, and pull requests—all different aspects of having multiple people working on the same code simultaneously.
- Honestly, I'm having a hard time coming up with any cons or things I would change.
- Version control system GUI is great
- Open-source support
- Pull request reviews are easy
- Conflict resolution interface is helpful
- UI could be a bit easier to use, especially the tabs on the pull request page
- Version Control: GitHub, being built over Git, makes it fast and easy to develop projects in versions/branches and easily rollback to previous versions when necessary.
- Pull Requests/Review: GitHub has a powerful UI for creating pull requests, with useful tools like inline commenting and more recently "suggested changes". Pull request history is always maintained and easy to search.
- Collaboration/Auditing: It's easy for multiple team members to work on the same project and merge changes (often) seamlessly. All contributions are tracked so it's easy to identify contributors.
- Industry Standard: GitHub is used by virtually all major open source projects so it's very easy to find and contribute to projects of interest if you're well versed with GitHub.
- Reviewing large pull requests can be tedious and it can be tough to identify recent changes (e.g. a one line change) in new files or files with lots of changes.
- It should be a bit harder to push unresolved merge conflicts, we've had these slip through once in awhile.
- You have to be careful with merge operations; a bad merge can be painful to reverse.
- Pretty much any development project (solo or as a team, it's always useful to have backups/project history; you never need to worry about losing your work if you commit/push regularly)
- Projects involving multiple collaborators with and a structured text-based syntax
Situation where Github is less appropriate:
- It's less useful for situations where you have multiple collaborators working on written/formatted reports; I've found Git can produce some nasty merge conflicts in these situations
- Central repository for tens of thousands of open source projects, making it very simple to contribute to those projects
- Desktop and web clients are robust, simple to learn, and easy to use
- Reliability is solid and we never have to worry much about Github being available
- Github's status as an industry leader means it's often targeted by sophisticated attackers with DDOS attacks, which has kicked it offline a handful of times in the past few years
- Lacks first-party support for mobile (no app component)
- Uncertainty in how Microsoft will manage the company post-deal-close
- Keeps history of our code
- Allows sharing of branches easily
- Can't think of one
- Simple and intuitive.
- Broad set of features.
- Conflict management could be improved.
- Searching is good but not great.
- User friendly
- Clean UI/UX
- Great documentation
- A lot of hooks into other services
- Discovering new repos could be improved
- Version Control
- Code Repository
- Ticket Tracking
- UI for non-technical users
- The ability to access GitHub on multiple platform makes organizing files very easy.
- GitHub is intuitive enough to help new users immediately understand its platform and how to use it. It has instructions and help notes at every turn to help with this and the UI is user-friendly.
- The best aspect of GitHub in my opinion is its ability to track your activity and also shows you a working map of of your activity over time. This can help with planning and scheduling of one's work.
- I think GitHub should incorporate two-factor authentication to improve user account security.
- The Macbook GitHub application could be improved to be more intuitive.
- Version Control - You can see the progression of where you started to where you are today, and if need be, rewind to a certain time in the past and use that version if need be.
- Storage Space - There are really no limits to the amount of information you can keep in one place.
- Collaboration - Contributors can be one or can be many, and GitHub keeps track of each instance by the author.
- UI - Although there is a readme file that can be made to look pretty, over the UI is very dry.
- App or web app - If there we an easier way to integrate with GitHub versus the command line, I am sure the number of users would increase dramatically.
- Glossary of Actions - There is not one place to which one author could go to find an absolute glossary of what actions do and what those actions are. Very hard to decipher the amount of information available on the web.
- GitHub makes it easy to research and find what code changed and when.
- GitHub is easy to integrate with other tools.
- GitHub is reliable and dependable. I've used it for nine years without issue.
- When browsing history of a file, GitHub could make it easier to see the file after a particular commit instead of just being able to quickly view the commit. I'd like to be able to see the commit or the file itself in one click.
- I would like to be able to view commits by user.
- I would love to be able to traverse code on GitHub (go to definition, etc) - the good news here is that they are working on these features!
- It's easy to use and has a very intuitive platform on the web.
- There's a whole bunch of tutorials online about how to use GitHub via the command line.
- Anyone who codes can create a free account on GitHub and start contributing with code.
- We can only have one private repository with a free account.
- Integrations with services like Heroku that allow us to deploy staging environments from a pull request.
- Familiarity with other developers making it easy to add a collaborator to a project and have them make a productive impact on the project right away without learning new tools.
- It makes it easy to review and collaborate on open source projects and private ones.
- It has many GUI client options for those who are not as comfortable with the command line.
- Helpful reporting of contributor activity and built-in project management features like docs and comments.
- In some ways, the design of GitHub incentivizes the use of certain practices like using pull requests, which may not fit your organization's workflow (though I don't really see this to be an issue personally, and if your organization isn't using something like pull requests, then I would question why).