GitHub Reviews

Pros

I work as a software engineer for a large consulting company, but as a side job, I teach a programming class. I use GitHub to share with my students all of the sample code and slides that we work on during our classes.

To me, one of the most important features is being able to work on my projects on multiple devices, than span across different operating systems. I have a two laptops (one of which is a Mac!) and a desktop computer. With GitHub, I can quickly sync my code and documents between devices and seamlessly pick up were I left off.

If I ever make a mistake and need to go back to previous versions of my slides or code, I can quickly restore them with the excellent versioning features.

For my students, it is very freeing knowing that every project or problem that we solve during class will be immediately available to them right after class. I helps them concentrate on learning and understanding the programs instead of having to copy everything to their computers.

Cons

The initial learning curve is high... specially if you are new to code collaboration tools. Newcomers usually spend a long time learning the git commands, and how they can solve problems.

For newcomers, I would recommend the GitHub Desktop client (even if it is frowned upon by more experienced devs), to get a hang of how the branches, commits, push, pull and operations work.

Alternatives Considered

Dropbox Business and Bitbucket

Reasons for Switching to GitHub

GitHub is the most reputable repository tool on the market. It uses industry standards and it is very secure. Also, it supports a wide range of programming languages, so it is ideal to host any type of open source software.

Pros

It is the primary and well-known version control option in the industry. You will always find an easy tutorial to set up anything you need, from fundamental to expert courses, since everyone knows about it and has used it at least at some point, so we are all well aware of its importance.

Most technologies and web applications can integrate with it. Using some CLI commands and simple yet powerful configuration files, you can set up a complete CI/CD pipeline in seconds. It is really an excellent option overall.

Cons

It might be intimidating at first, and for nontech professionals, it might seem something that might as well be in a different language because there is not an easy onboarding process to understand its structure, purpose, or level of abstraction. It might require some guidance initially, but once that learning curve is surpassed, it will become something easy to relate to.

Pros

GitHub has a user-friendly interface for managing repositories and navigating projects. It makes collaboration easy with features like pull requests, code reviews, and comments. GitHub Actions lets users automate workflows, making continuous integration and deployment easy.

Cons

The interface can be overwhelming and difficult for beginners to learn. It will be complex to manage large projects. Setting up integrations can require extra effort.

Pros

- free private repo is cool
- Github actions is awesome
- Github pages saves a lot of money for web apps demo & open source projects. I myself have hosted all of my open sources web apps on Github pages.

These are my favorites. Rest I can go on and on.

Cons

- Search feature is lacking. If there was better search functionality (eg. [SENSITIVE CONTENT] - powered by algolia), it would be a lot helpful. Searching one report among thousands is a pan right now.
- Dependabot is pain
- Sometimes Github pages doesn't update properly
- Don't get relevant projects on "Explore repositories" section

Alternatives Considered

Bitbucket

Reasons for Choosing GitHub

Github was better, in terms of free features and the UI.

Switched From

GitLab

Reasons for Switching to GitHub

GitHub has a lot of cool features for free.

Pros

Source Control is the most I like in GitHub. When we work with team, source control is important. All of team members will be pushed their codes at the same branches. If I am owner of project I will look up their code and accept their pull requests.Github's source control is easy to use to combine codes from each member. This is the one I like Github.

Cons

I think Authentication. I am a software developer and I use VS code as IDE.Github can authenticate with VS code. I have to GitHub account, one for personal and one for office work. When I was changed my personal to work account or vice visa, I'm faced with some issue that is git conflict among two accounts.I am worked with my office account, but in authentication, my account is still personal account. I think this part is needed to update about Github. This one is I like least about Github.

Pros

It works. Fast and on Mac OS, Windows and Linux. Integrated nicely into both Visual Studio Code (PC, Mac) and Visual Studio (PC).
Code compare. Merge. No problems.

Cons

It starts to eat disk space and 50Gbyte gone the other day. Some more integrated cleaning would be great.

Pros

I love the wide array of features and the usage simplicity. Everything works well and meets pretty much all of our needs as a team. GitHub is very dependable and does a great job at constantly improving and responding to feedback.

Cons

CI/CD is a bit of a rabbit hole that I wish the barrier to entry was a little lower on, but all the right tools are there if you spend the time to learn them.

Alternatives Considered

GitLab

Reasons for Switching to GitHub

More polished website experience and more features, tools, and customization.

Pros

User Friendly , Ease To Setup , Customer Support, Code Review System.

Cons

Pricing, Art Asset Management, Unity Engine Specific Support

Alternatives Considered

GitLab and Bitbucket

Reasons for Switching to GitHub

Rich Community Support , Very Good Code Review System

Pros

The ease of version control, the ability to track changes, and also the seamless way it allows multiple people to work on the same project. The availability of open-source projects and the ability to learn from others' code, is also a huge plus. It helped me a lot in my research.

Cons

It can be a learning curve for beginners. The interface can be a bit overwhelming at first, especially for those who are new to version control or command-line tools. Also, navigating through large projects with many branches and pull requests can sometimes feel overwhelming.

Pros

Enables seamless teamwork with multiple contributors. It tracks and records all changes for easy rollback and review.It also facilitates features development and bug fixes without affecting the main codebase. Large community support and extensive documentation.

Cons

It can be difficult for beginners to master.It's advanced features can be overwhelming for small projects. Private repositories require a subscription for more advanced features.

Pros

Very easy to host a repository and to fork other repositories. It is easy to search other repositories.

Cons

None that I found. My only request would be to be easier to download single files without having to view the file first. If there were checkboxes and a download option that would be great.

Alternatives Considered

GitLab

Reasons for Choosing GitHub

Github has a much better repo interface than Bitbucket in my opinion.

Switched From

Bitbucket

Reasons for Switching to GitHub

I was so happy with GitHub I hadn't looked closely at the most comparable option, GitLab, which requires me to learn a new interface and functionality.

Pros

Github requires no introduction. It is the most popular source code management among opensouce and enterprise customers. It has native integration with almost all cloud providers.

Cons

Charge per user. In our case we outsource 70% of our development to outside contractors. Every time we add them into our account, it is considered as additional collaborator and takes away one seat. It will be hard for us to keep monitoring both internal and external developers on our team to keep the cost under control.

Alternatives Considered

Assembla

Reasons for Choosing GitHub

Most of the developers we hired in the past were not familiar with Assembla and hard time convincing them to use it. It was not as popular as GitHub in the developer community.

Switched From

Assembla

Reasons for Switching to GitHub

Reasons are mentioned in the previous question.

Pros

GitHub has grown leap & bounds over the past few years. They have always offered really excellent tools for developers that is well built and very stable. More recently GitHub has put a lot of effort in creating a more intuitive user experience that makes it simpler to use for both beginners and experienced users. As a designer who isn’t the best with code and development but still knows how to setup and deploy code with GitHub there updates over recent years have been very helpful in day-to-day. Integrations & security settings are excellent as well.

Cons

Nothing much to say here. GitHub can be a bit overwhelming for a beginner but IMO they have been addressing this and making it much more comfortable to get started using. I’d like to see more of the same in other areas as well. Solving merge conflicts in GitHub was the only time I was ever frustrated with the tool.

Pros

Github is secure, promotes collaboration and is free for the most part. The core features of git is free and for further more "niche" features you can get enterprise. Github is great to go and check how you dependencies work in projects that you use and to see anything from issues to versions related to the source code

Cons

One (I want to say annoying) thing is that all the repositories is stored in one place. I would love to just be able to separate personal projects with fun projects and shared projects with the use of a folder structure.
Also difficult to get a hold of GitHub documentation, i found myself learning trough Youtube videos instead of practicing from a document page (I am sure there is but i could not find it)

Alternatives Considered

Azure DevOps Services

Reasons for Choosing GitHub

Licenses are expensive and limits the number of members in our team.

Switched From

Azure DevOps Services

Reasons for Switching to GitHub

Free to use. Secure and popular.

Pros

Users can manage their time more efficiently by doing code versioning and code review.

Multiple developers can stay in sync with each other and can develop their software products in collaboration with one another.

Open Source software products can be created, accessed and improved publicly and developers can contribute to the Open Source project from anywhere in the world.

GitHub can be used as a resume as it helps with visibility and reputation building for developers by allowing recruiters to view their interesting projects when applying for job opportunities.

Cons

The intial learning curve can be tricky for new users. Onboarding requires a bit of detail and practise with regards to cloning repositories, creating a fork/ branch, pushing changes to code and raising pull requests when getting started, but once this process is well understood, the product is easy to use.

Alternatives Considered

Slack

Reasons for Switching to GitHub

GitHub is more widely preferred and used by software developers globally, uses less bandwidth and provides visibility of projects for future version improvements and for recruitment.

Pros

First of all it got very simple, easy to understand and user friendly user interface tool that can be user by anyone within hours of it deployment. Most of the functions can be accessed with both command line and through dashboard too. Also CI/CD is one of the best feature that it provides and reduces manual efforts of code deployments. It provide supports for almost all languages and even it raises mail for some security vulnerabilities found by it. Best part you can have both public and private repos.

Cons

There is no any such issues I have found. Just few features are there for which you need to pay.

Alternatives Considered

GitLab

Reasons for Choosing GitHub

The UI was bit complicated to understand for team.

Switched From

GitLab

Reasons for Switching to GitHub

It is very user friendly tool and there are lot of open source features provided by it.

Pros

GitHub continues to improve with tools focused on helping developers. The base account that is free offers tons of features. When you are ready to test out the paid features, the value is there as well. I like that it is an optional upgrade since not every organization needs them.

Cons

When someone says 'GitHub can do it', it is getting harder to know if it is GitHub Free or one of the paid options. If you aren't following GitHub's releases, you can get left behind quite quickly.

Alternatives Considered

GitLab and Bitbucket

Reasons for Switching to GitHub

GitHub's free option satisfied the need and nailed the features we were using. Once trying it, we didn't look any further.

Pros

Since GitHub relies on Git underneath, one can be assured that it uses a strong, open source system behind the scenes. It integrates so well with the command-line that it's the main way I interact with GitHub on a daily basis. All essential actions you may need to perform are also available in the graphical interface on GitHub, making for a convenient experience when on the move as all necessary tools can be accessed either way. It offers security features such as the ability to link SSH and GPG keys, allowing users to verify their commits and secure their identity. The two-factor authentication system is also impressively well thought-out, having various recovery options including security keys, SMS number, recovery tokens, recovery codes and even fallback SMS number. If you often write the same content in form of comments, there is even a feature to have "saved replies", speeding up the interaction process for recurring matters. GitHub is also extremely accessible, offering unlimited private repositories for personal use. Even open source organizations can benefit tremendously without having to spend a dime as it includes by default everything one can need. GitHub is also perfect for students, giving you access to pro features and discounts through their "Student Developer Pack". GitHub Pages is another fantastic aspect of the platform, allowing you to host a website without any hassle, with really quick build time while also ranking very high on search engines.

Cons

Even though all members in a specific organization on GitHub may prove they are all verified students, there is still the need for the educational institution to set up a few steps on their own to approve changes being made, which slows down considerably the initial setup. The search options, although they are powerful, aren't very intuitive and many useful functions are well hidden in the documentation pages. As a regular user, there is no option to freely start collaborating in private repositories before scaling up, which is a feature that's often available on other similar platforms. On that note, the price tag for GitHub is relatively high for the added benefits compared to other solutions. There is a restriction on file size, which cannot exceed 100 Mb. In most instances, this is not an inconvenient, but it will not be an appropriate platform to handle sharing large files when rendering 3D models for example.

Pros

Knowing git and GitHub boosted the productivity of my team members and I. We were able to cutback on the times we were doing manual version control work rather than actual software development. It has been very useful to the point that it has been integrated into our project work pipeline. It has been very reliable and our team has never encountered problems in uploading and retrieving the code of others. We are able to document any changes to our code and fix conflicting code which made working in a team much more convenient.

Our team of 3 uses the free version which allows us to collaborate with each other, set up a public or private repository, document our bugs, and manage our workflow which already is a lot for a free service. Paid options allow for collaboration of bigger teams, analytics, and other advanced features.

Aside from that, a GUI version of the application allows you to visually see the changes in the project and simplifies the workflow. Tutorials and documentations on how to use GitHub, for both the GUI and command line versions are available. Most source code editors now even have GitHub integrated and allows you to do the commands without leaving the editor.

Cons

As great as GitHub is, it really takes some time in getting used to, especially for beginners. It has a steep learning curve and you are most likely going to have to use a search engine for the tasks you want to do. GitHub also has an application with a GUI which is relatively beginner friendly, but even then, the Git workflow is really something that requires practice. I personally use the Command Line Interface and the difficult part is knowing the commands to use in which I solved by printing out a cheat sheet.

Pros

GitHub has so many features and if you are a college student you can easily apply for their educational pack and receive many free packages from other software and free access to GitHub Pro for as long as you are a student. This pack comes with free domains, a key for JetBrains IDEs, Canva Pro and other packages to assist you in application development.

In addition to the free services provided by GitHub for college students, it also provides many functionalities for general users. You could easily integrate your codebase to services such as DigitalOcean and Heroku to create pipelines and automatically deploy changes. No more tiresome setting up of servers and bothering with them for every deployment.

GitHub also has the functionality of creating pull requests, issues and assigning issues to people. They also have GitHub Projects where you can create Kanban boards and assign tasks to the team members. Pull requests can also be reviewed and comments can be added for specific lines.

This is also the home for many open source projects that you can find and contribute. Most companies view your GitHub profile to get an idea of your projects and how you have contributed and worked on projects.

Cons

There really isn't a major feature that you could point out and say is bad. The only downside I would say is, although they do have a free tier, the number of private repositories you could have in that tier is very limited.

Many people would say that the commands are hard to get a hang of but this isn't a downside of GitHub, the commands are by Git. Git is inherently complex and to be honest, GitHub does a very good job at trying to simplify it.

Pros

Commonality is the principal word that rings a bell, for a little, quick yield group. We needed to zero in on conveyance, not the cycle and Github gave what we really wanted - source code the board, cooperation, project the executives the most straightforward, and the least expensive. While its rivals like Bitbucket have tried to focus on the undertaking business sector and spotlight for enormous scope corporate tasks, Github is significantly more little group amicable as there's no additional stuff of sorting out the stage, and rather, we can simply zero in on doing what we came to do. Github activities fit our assemble needs genuinely well, and coordination with arrangements like Netlify for CI-CD was a breeze. Venture the executives is basic and simple. The open source well disposed guideline helps in simple admittance to new and coming code content lined up with our inclinations to investigate and use in our own applications and items, something that needs other SCM items

Cons

A reliable documentation framework like Confluence would be truly useful. As groups develop bigger, they shift to elective arrangements since Github needs more usefulness to oversee assignments and code across the bigger group, which can be changed by getting highlights and working on existing ones. Incorporation backing can be extended rather than keeping it restricted to inhouse items.

Pros

I find the whole GitHub model quite refreshing. In a matter of seconds, I am able to create an account, create a repository and get instructions on how to set it up on my computer. The introduction of the GitHub desktop made things even simpler. Project tracking, graphical progress representation (commits, issues, pull requests and the timeline), project boards, automated deployment, seamless integration, webhooks, bespoke security keys and CI/CD are among the many functions that GitHub is able to perform. All major IDEs nowadays have the option to integrate with GitHub accounts directly and initialize Git for every new project you start making source control a seamless process. I love the immense collaboration tools and the fact that it works with many existing workspaces such as Notion, therefore, making product development quick and effective.

Cons

GitHub needs to add more integrations to ensure new users have a smooth transition from other products so that work done before onboarding is not lost.

Alternatives Considered

GitLab and Bitbucket

Pros

- I liked the version control system in GitHub, which allows for easy collaboration and tracking of changes made to the codebase.- I liked the integration with other tools and services, such as continuous integration and continuous deployment (CICD) systems, which allows for seamless integration of machine learning models into production environments.- I liked the community features such as finding and sharing code snippets and libraries, which can be incredibly useful for data scientists and machine learning engineers.- I found the software easy to use and navigate.- Integration with existing business processes was seamless.- The Access controls and Permissions feature was impactful as it allows for granular control over who can access and make changes to a project, which helps to ensure that only authorized users are able to make changes to the codebase.- The debugging feature was also impactful as it allows to see the history of changes and allows to revert back to previous versions if needed.- The task and project management features were also impactful as it allows developers to easily manage and track tasks and issues associated with a project, which can help to improve productivity and collaboration.

Cons

- One potential downside of GitHub is that it may have a steep learning curve for new users who are not familiar with version control systems.- Some users may find that the UI can be cluttered and overwhelming, making it difficult to find the specific features or options they need.- Some users may find that certain features or integrations are missing or could be improved, such as more advanced collaboration tools or better support for certain programming languages.- Some users may find that the cost of using GitHub's advanced features or integrations can be prohibitive for smaller or less well-funded projects.- There could be more customization options for the dashboard and reporting/project tracking feature.- For non-technical users, the interface may be challenging to understand.- The SSL security feature could be improved to provide better protection for private projects and data.- Some users may find that the bug tracking feature is not as robust as other issue tracking systems.

Pros

Version Control: GitHub provides Git-based version control to manage projects and track changes.Collaboration: GitHub allows multiple users to collaborate on a single project through pull requests, code reviews, and issue tracking.Project Management: GitHub provides a platform for managing projects through its built-in project boards and kanban boards.Code Hosting: GitHub provides unlimited private and public code repositories for hosting and sharing code.Documentation: GitHub provides a platform for creating and sharing documentation for projects.Integrations: GitHub integrates with various tools and services, including continuous integration/continuous deployment (CI/CD) tools and project management tools.Security: GitHub provides security features such as access control, code signing, and security alerts to protect projects.Community: GitHub has a large developer community, making it easy to find answers, collaborate, and contribute to open-source projects.

Cons

Cost: For private repositories and advanced features, GitHub requires a paid subscription, which can be expensive for individual users and small teams.Limited Storage: GitHub has limited storage for larger files, and it can be difficult to manage large binary files or backups on the platform.User Interface: The GitHub user interface can be overwhelming and confusing for new users, and some advanced features can be difficult to use.Dependence on Internet: GitHub requires an internet connection to use, which can be a drawback for users with limited or unreliable internet access.Limited Customization: GitHub has limited customization options, and it can be difficult to integrate with other tools or modify the platform to meet specific needs.Performance: GitHub can become slow or unresponsive during periods of high usage, and some users may experience performance issues when working with large repositories or projects.Privacy Concerns: Although GitHub provides security features, some users may have concerns about privacy and the security of their data, especially when hosting sensitive information on the platform.

Pros

GitHub provides an exceptional environment for collaboration among developers. Its intuitive interface allows for seamless communication, issue tracking, and pull request management. With features like code reviews, team discussions, and project boards, it fosters a collaborative spirit and enables developers to work together effectively.

Cons

While GitHub is a powerful platform, it can be overwhelming for newcomers, especially those unfamiliar with version control systems. The concepts of branches, pull requests, and forking may require a learning curve, which might discourage some beginners. More comprehensive documentation and guided tutorials could help mitigate this issue.