Filter Ratings and Reviews
Filter 490 vetted GitHub reviews and ratings
Reviews (1-25 of 109)
February 11, 2020
GitHub is currently a top cloud based SCM
GitHub is used throughout the organization as cloud based SCM. To enhance and automate the SDLC process as much as possible, features such as branch protection, mandatory code reviews, and continuous integration checks are used whenever possible. As a cloud based SCM solution, it provides the security and redundancy needed in an SCM solution.
- Different offering for continuous integration providers
- New features (code owners, branch protection)
- Bring the social aspect of programming into focus
- Lack of command line configuration options (everything is GUI based)
- Downtime (not infrequent, no data loss, but still a pain)
- Improved security scanning (for keys in history to prevent merges, etc)
We use Github extensively for version control and team collaboration in all of our development/architecture projects. It's primarily used by our product team but we also use it to share information with the success team and collect feedback. Github assists us in the process of code reviews and is a powerful tool when managing/deploying multiple simultaneous projects.
- 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.
We use GitHub as a central source control repository for all client engagements. GitHub allows our global teams to collaborate in real time through its best-in-class tooling and simple to use interface. Github also serves as the main integration point with other pieces of software, including integration into continuous integration and continuous deployment services.
- 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
January 06, 2020
The best source code management platform
We're using GitHub for our entire software workflow cycle including code versioning, code review and approval, team collaboration on the code, and release management. Now, with actions, we're also building our Docker images and deploying them live, so it's a full CI/CD pipeline for us, all in a single package that's used by the entire development team.
- Simple and intuitive.
- Broad set of features.
- Conflict management could be improved.
- Searching is good but not great.
January 27, 2020
GitHub makes Git very easy to use
All engineering teams use GitHub for version control. It is integrated with Looker, JIRA, Jenkins, and all DevOps tools along with all popular IDEs.
- Keeps history of our code
- Allows sharing of branches easily
- Can't think of one
October 15, 2019
GitHub is the standard for a remote GIT repository
We are using GitHub in our development team as our source control solution. GitHub allows us to easily work from either the office or remotely. Git's distributed version control makes branching incredibly easy, and GitHub provides the most seamless and easy to use Git solution I have found. GitHub provides a ton of integration options with any tool you are using.
- 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!
October 12, 2019
GitHub is Everything You Need for Version Control
The development department uses private GitHub organizations for version control of web applications and internal analytics programs. Only development uses it, the other departments do not create new code or interact with it so it's only been appropriate for us.
- Code difference comparison
- Private repositories that are stored outside the organization
- Code highlighting for ObjectScript
- Issues tracking is easy to attach to commit history
- Syntax highlighting for more obscure file types, like csp (Cache Server Page)
- Better handling or notification of deleted forked repos. If you delete the repo, the pull request will show up as "unknown repository" which creates odd dead ends
October 10, 2019
Solid and reliable code version control system that makes distributed collaboration easy.
GitHub is our primary code repository for the company's web app. It allows us to effectively collaborate as a team on our codebase, while providing an easy system to track and manage changes. GitHub essentially serves as the Google Docs for our code. Specifically, it allows multiple software engineers to work on the same code in a separate environment that protects the primary codebase and is only merged in when it's working as expected. This allows for all kinds of collaboration, including with remote workers all over the world.
- GitHub's ease of use is one of its biggest strengths. The site is structured around Git, a code version control system, which is used by developers around the world. GitHub's UI is minimal and allows you to focus on what's important, whether it be your branches, pull requests, or issues.
- GitHub's integrations and tools are fairly ubiquitous. You'll likely find an integration with GitHub on every development tool with integrations. This makes it easy to incorporate in whatever workflow you may have.
- GitHub is incredibly reliable. I don't remember the last time it was down for any significant period of time. This is essential for companies that rely on it for their daily operations.
- While GitHub's spartan UI gets the job done and doesn't distract, it has some room for improvement to make things even more intuitive, especially for newer users. There's a certain amount of learning curve that could be made less steep.
- There's so much you can do with Github that it's fairly common for a user to possibly only use a small fraction of what GitHub can do. Improving Github's discovery features would help surface some of the non-essential features that are quite useful.
October 24, 2019
GitHub: a product so perfect it's become synonymous with Git
GitHub is used by some development teams across our large organization, including our small web team. It's used as a central code repository for storing our website code and allows multiple developers to work on separate branches simultaneously, then merge those changes into the main branch once their work is finished. It also keeps a history of changes so we can tell who changed things and when they were changed.
- 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.
October 15, 2019
I would highly recommend GitHub!
GitHub is being used by the information technology department to work concurrently on projects we are looking to implement in the coming months. It addressed the issue of having to work together and input code from various locations.
- 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.
October 15, 2019
There is no other Hub like this one!
Github is being used for version control and feature branches for our main website. The tech team is the only person with access to push or pull from the repository. Our industry is changing very rapidly, and so, the tech team is charged with adjusting our front-facing website hourly, and sometimes this causes conflicts when one of the team members is also doing a similar task. Thus, GitHub allows us all to stay in tune and be in perfect unison when it comes to deploying code out to the web.
- 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.
October 12, 2019
The best hosted version control and software collaboration tool
Our design and development team uses GitHub. About 10 years ago we used to use SVN instead of Git and we tried some cloud services for hosted SVN repositories. At the time we felt that Git was more focused specifically on open source software projects, didn't have GUI clients for designers, and didn't have the project management-oriented features that we wanted. That has completely changed since then, and now Git and GitHub specifically is the perfect solution for our team. GitHub helps us build great software, and integrates with many services we use to help us be more effective with a distributed team.
- 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).
GitHub currently isn't the main product we use for hosting our repositories. We primarily use Bitbucket currently and have plans to move to Azure DevOps whose repository hosting/management is re-skinned GitHub. My use of GitHub has primarily been working with open source libraries.
- I prefer the way GitHub presents/manages code reviews.
- Making changes and opening pull requests are incredibly easy in GitHub. When you have a small change you need to make it's incredibly annoying to have to pull then branch then commit then push then go back to the browser to open a PR.
- Built-in wiki, issue tracking and reporting, and other tools can be incredibly useful.
- Browsing through a repo is pretty primitive. Digging into a folder is a link to a new page. For medium to large repositories, it's extremely cumbersome. The way Azure DevOps manages this is incredible. It gives you a folder explorer as you'd find in VS Code. You can quickly browse through a complex repo and make in line changes and submit a pull request all from inside the browser.
- Navigating around a GitHub repo can be a little confusing until you're used to it.
October 12, 2019
GitHub has revolutionized the web development workplace
Git Hub is not used in any official capacity but there are numerous staff (developers), instructors and staff that use this industry-standard platform for sharing code and working collaboratively on websites and apps.
- Great for sharing code and collaborating with the coders around the world.
- Versioning: By installing Git on your local machine and taking a regular snapshot (called commits) you can restore your project to any previous point without having to keep multiple versions of your files.
- I consider GitHub to be social media for coders/developers if social media was actually useful. There are tons of free resources and the community is fantastic.
- With GitHub you can host a simple static website for FREE (which is better than AWS s3 buckets IMO)— this is a great alternative to vendors like GoDaddy or BlueHost, etc.
- The UI isn't super intuitive at first but help is easy to find.
October 11, 2019
The best choice for hosting code online
All our source code is hosted in private GitHub repos. All code reviews also go through GitHub and our deployment process goes through GitHub as well, pushing to the master branch triggers a GitHub webhook that deploys the code to production.
- Excellent integration with CI/CD tools: testing and deployment are easy via GitHub's ecosystem.
- Great code review tools.
- Easy to link to and share specific lines of code to communicate with engineers.
- Notifications are noisy by default and hard to configure to do what you want.
- No cross-repo issue tracking, hard to see all open pull requests at once.
- We pay per seat, which means sometimes we introduce extra friction because we can't give everyone access to our GitHub.
October 10, 2019
GitHub: Version Control for the Masses
We currently utilize GitHub as the default code repository host for clients who either don't have a current version control system or for internal projects that need hosting. It's primarily used across our whole delivery team, while projects from other departments may be hosted there as well.
- Github integrates really well with 3rd party systems, especially those used for continuous integration.
- Github provides a number of built-in tools to support the project management process.
- Github is ubiquitous in the sense that it's rare to find a platform or organization that hasn't used it, making it much easier for onboarding.
- Some of the extended features, like "Projects", can be a little too lightweight and users may spend too much time setting it up and not end up using it.
- The process for accepting invitations is kind of odd and doesn't always provide direct instructions to end-users.
October 09, 2019
Keep Your Code in the Cloud Without Sky-High Pricing
Our department uses GitHub as its dedicated private repository for our production-facing web applications. In general, GitHub is popular across our organization (a public university), especially for students. GitHub gives us a high-quality, secure, cloud-based Git repository system at no cost, allowing our team to safely store application code, and to pull updates to our test and production environments, with minimal effort.
- GitHub is a great, free or low-cost cloud-based Git repository system for smaller teams; it's easy to add members and collaborators to one or more repositories, as well as to modify user roles and rights.
- GitHub provides a handy and highly transparent front end on top of the renowned Git system. Visibility into developer productivity, including code commits, is well-represented in GitHub's dashboards.
- GitHub provides extremely detailed and focused user support documentation online, allowing every team member to build their Git skills incrementally while ensuring that most basic issues are handled quickly via end-user self-service.
- GitHub packs a lot of functionality into its website; sometimes it can be difficult to navigate to the correct sub-page; the various drop-down selection boxes and sidebar menus can be confusing to users, especially ones with lightweight experience with the interface.
- GitHub allows for substantial flexibility in user account management - Administering dedicated team members and collaborators across a large number of repositories can get tricky, especially if users have varying access rights or roles across various repositories.
- Knowing the difference between user and organization accounts is key, there have been many times where I've wasted minutes looking at the wrong account trying to find a relevant setting or feature. For example, to view correct account billing information, one must be on the organization account, not the user account that has administrator rights for the organization.
GitHub provides us with access to open source software and small scripts of code that we can use instead of writing the code ourselves. Knowing that the code is critiqued and improved by other developers and generally follows best practices, this allows us to analyze it's suitability and compatibility quickly. GitHub provides logs of the changes to this software to assist in bug finding and allows us to contribute to the software if we require a change.
- GUI for source control is great.
- Storing source code efficiently with simple commands.
- Searching for code is in a code base is easy and works well.
- Atom takes too long to load.
October 09, 2019
Friendly UI with lots of features
GitHub is primarily for managing software source control, issue tracking, developer collaboration, CI/CD. We use it for source control, peer review, and server-side merge, CI/CD capabilities like automated test suite running for PRs and merges. We use a separate issue tracking system, but for many projects GitHub's built-in issue system is adequate, it has advantages like automatic issue references and linking of issues to commits, PRs. GitHub also offers wiki pages per project, team organization, and one of my favorites is its free static website hosting service called (GH-pages). Their static hosting is capable of consuming Jekyll (Ruby on Rails) based projects on the server-side. Open-source repositories and organizations are free of charge with a 1GB limit per repo. A limited number of private repositories for individuals (not organizations) are also free. GitHub can perform security checks of the packages used by the project and even propose recommended fixes to those in the form of generated PRs. Speaking of automated PRs GitHub offers extremely easy few click solutions to contribute bugfix PRs to open source projects and other actions can be performed solely using the web front-end.
- Free hosting of open source projects and a limited number of private repositories as well for individuals.
- Free website hosting of statically generated websites or Jekyll Ruby on Rails-based projects.
- Issue tracking, pull request system.
- CI/CD capabilities.
- Enforcing rules like PR needs to be accepted for a merge and other team management and policy features.
- Widely adopted, large user base.
- Very friendly and easy to use UI, many tasks can be done through the web.
- Organizations without a paid plan cannot have private repositories.
- Free repositories have a size limit of 1GB.
- Support could be slow to respond.
- Migrating repositories to other services can be hard.
October 09, 2019
One stop tool for all Coding tactics!
GitHub is the most used tool in my team. I have been using this for a long time. I am really excited about committing updates to open source community and getting green commit dots on my profile as these green dots reflect your active time on GitHub. Every new update in our program, we commit to GitHub.
- Multi-platform support, Linux, Windows and Mac.
- Growth to Open Source Community.
- Recruiters can check the GitHub profile than reading the complete CV. Even I prefer to share my GitHub ID than complete resume. As GitHub is your new CV.
- Best way to showcase your talent to open source development.
- GitHub requires attention over an android app. There are numerous third-party applications but not an official application.
- GitHub requires more improvement to make it industry ready app.
- One cannot use only github in their company for real time and live databses and applications.
At our company, all Engineering and Product Design team members use GitHub. We use its code repository, version control, and ticket tracking tools to store, maintain, and manage code for various projects. It works incredibly well at all 3 functions and is an extremely vital tool for our entire organization.
- Version Control
- Code Repository
- Ticket Tracking
- UI for non-technical users
October 09, 2019
GitHub - Versioning Control
After cloud migration, GitHub becomes obvious for use, especially its automation. The whole organization is using the GitHub as a hub. It works like a Repository where Developers, DBA, and QA keep their artifacts; and make them visible or accessible to the team. It works as a shareable location for the team. It works as the shareable location for all automate jobs. GitHub is a great Hub.
- GitHub is a place where we can keep the artifacts such as source code, lookup data, and other callable information. GitHub can be integrated with deployment tools such as Jenkins, TeamCity and any cloud DevOps tools. These tools can call/read the code or data from GitHub which works as a hub or repository.
- GitHub works as version control. Meaning, when you upload the code script with multiple changes, the GitHub stores old copies as versions. If you want to restore back to the point-in-time code script, GitHub provides you to restore it. So GitHub gives security over your code.
- GitHub provides public and private access. Public is free. Private charges. For proof of concept projects, development or testing, we can use PUBLIC access which is cheap or free.
- GitHub is great tool. when you want to push a code change or small update, you would need to required to pull the entire GitHub repository unto your PC. This need to mitigate.
August 01, 2019
Amazing Tool for not just developers but for PMO too
In our org, GitHub is not just used by developers but also by PMO teams to version control the documents which has a fabulous controlling which helps in maintaining the content of the files.
As per its flagship functionality of forking which is duplicating a vault starting with one client's record then onto the next - this empowers us to take an undertaking where we don't have compose access and change it under our own record. In the event that we make changes we'd like to share, we can send a warning called a "pull demand" to the first proprietor.
As per its flagship functionality of forking which is duplicating a vault starting with one client's record then onto the next - this empowers us to take an undertaking where we don't have compose access and change it under our own record. In the event that we make changes we'd like to share, we can send a warning called a "pull demand" to the first proprietor.
- Fork
- Pull Request
- Merge
- Only for premium users to use
- File size limitations
- Private repositories for free accounts
We use GitHub to host our code, back it up with source control, and as part of our software development life cycle via code reviews using the pull request feature. We also use GitHub to review the code of open source libraries and contribute to open source in general.
- Source control
- Reviewing code
- General ease of use
- Searching through code
- Outside collaborator functionality makes it hard to assign permissions correctly.
October 12, 2019
One of the best tools for software development version control
In my organization, GitHub is used by the development team, so everyone can keep track of the version control for the code we produce on a daily basis in projects.
- 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.
GitHub Scorecard Summary
About GitHub
Categories: Version Control
GitHub Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |