GitHub

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

It’s the most basic choice for a reason. Great, free in most cases, and provides great customization. I love github, I use it everyday, and I would recommend it over bitbucket, gitlab, etc. It provides a whole new experience. Almost like a social media VCS.

Cons

Honestly I don’t have any complaints to share. Github is just my favorite.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

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

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

Almost everything is free, user interface is very easy to use/understand.
I love the community support too, a lot of developers are giving some open source products on this website

Cons

Some basic features like the ability to create categories to organize repositories is missing. It is a very annoying problem and a lot of people asks to implement it since many years but GitHub does not say anything about it

Pros

- Ease-of-use
- Simple yet powerful UI
- Low price
- GitHub Student Developer Pack
- Wide Community that is eager to help
- Documentation and tons of guides
- Great support

Cons

- Nothing really comes to my mind, overall it's just great.

Alternatives Considered

Reasons for Switching to GitHub

Pros

Feature richness and integrations available

Cons

The code reviews process could be improved, for example the ways we can leave comments or code suggestions.

Alternatives Considered

Reasons for Switching to GitHub

Pros

GitHub has become an industry standard as a code management and repository software

Cons

Learning git push pull and commit can take some time to learn.

Alternatives Considered

Reasons for Switching to GitHub

Pros

It's free, it's the standard, and it's filled with almost everything you need.

Cons

The CLI tools can be a bit bizarre at times, but that's okay. Also it seems a little troublesome to set up keys at times.

Alternatives Considered

Reasons for Switching to GitHub

Pros

It is the base of so many open source projects.

Cons

Honestly I think it does everything quite right.

Alternatives Considered

Reasons for Switching to GitHub

Pros

Git hub provides you a platform to maintain your portfolio and your project all together. It also help in improving your CV for searching for jobs.
It helps you track your project involvement record. We can also use other persons project codes to help our projects.

Cons

Many a times private project are meant to be shared, and we cannot even ask to pull the code.

Pros

Github is amazing. I used to utilize Bitbucket a lot but Github was more robust and before the free tier for both was kind of equal. Now Github free offers unlimited private and public repo's where bitbucket only offers like 5. Github also seems to be a lot faster when dealing with branches and commits. Like the connection feels snappier. I can say the same for the website. Now where Bitbucket, the website used to be fast but ever so since the re-design it's a little more on the heavy side. I honestly like Github and I've moved all my code there to be hosted, since it's super secure and super reliable. For as long as I have used it (around 4 years now) I haven't had issues with accessing or uploading my code changes.

Cons

Please, link issue tracking with branches so you can see the branches that you made or the commits that you made for specific issues. Bitbucket/JIRA has this and is a god send for project management

Also integrate it with the boards, for instance, a linked issue when closed, it can auto-merge the branch. JIRA/Bitbucket also has this.

Alternatives Considered

Reasons for Switching to GitHub

Pros

- high availability
- built-in code review, wiki, issue tracker, artifact hosting (private beta)
- great third-party tool integration
- automate everything
- uses git
- developer friendly company
- free for open source projects
- mature

Cons

- issue tracker could be more sophisticated
- new features could be developed more rapidly (although this has improved recently)
- native apps are not up-to-par with competitors, but luckily there are many free alternatives
- was bought by Microsoft, I personally would have liked to see them stay independent

Alternatives Considered

Reasons for Switching to GitHub

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

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

Reliable and consistent version control and code collaboration platform. The team management, issue tracking, visibility/privacy control are all top of the line, and of course the underlying "git" hosting is perfect. Introduction of Github Actions only improves the value of the platform.

Cons

I'd like to see more for project management, e.g. ways to better organize issues by priority, themes ("epics") and create scrum, agile and/or kanban influenced views and planning tools. I've heard some folks express concern with Microsoft's acquisition of GitHub, but I don't understand the concern b/c Microsoft has a solid history of operating business-grade tools, and from the date of acquisition we've only seen more-for-your-money price changes.

Alternatives Considered

Reasons for Choosing GitHub

Pros

GitHub makes managing Git repos a lot easier by providing a fantastic UI and a solid infrastructure. I also love the Package Registry service which fast, reliable, quick to set up and use, and has a fair pricing plan.

Cons

There is very little to dislike about GitHub. I'd like to see more work towards code monetization (for instance by creating a unified platform that takes care of licensing and payments)

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

First, it has a desktop application, so it's easier to pull, push and track changes. It's free for private repositories and organizations (even if yours it's not an open source one). You have A LOT of integrations, like Slack, Jira, Jenkins, etc. Also, you can create your own integration if you need it.

Cons

I think the only thing is missing on Github is group repositories in folders. You can do something like that (using the teams feature) but at the end the repositories are not grouped.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Pros

I mostly like the ease of use and in the same time the big hand that Github gives me and my colleagues every day to
accomplish our daily tasks and be coordinated with each other.

Cons

To be honest I think that Github is the best code hosting platform and is very hard to find any disadvantage. I use it every day and I am happy.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

In addition to being one of the first platforms of its kind and a great choice for software project management, github went further and became a true developer network, the first one I guess. Many companies hire exclusively considering the particular repository of each developer what mekes the employees even more eggor to lear the environment.

Cons

Not much but yet a little above the price if compared to other rivals.

Alternatives Considered

Reasons for Choosing GitHub

Reasons for Switching to GitHub

Pros

My first interaction with GitHub has never been changed and made different following the impact it had on my project. The fact that I was leading a big team that needed to share and update file frequently, GitHub become a game changer and the source of success to us. When asked to use the software for any project any time, I would settle for this with confidence following the following facts

I went against the norm to compare the ability of the software and here are some of the reasons it remained on top for me.

-Very easy to get started use.
-Compatible with many other devices that are needed.
-Can be shared in a team simultaneously seamlessly.
-Organizes the work depending on the latest changes.
-Offers central view of the project leading to easy supervision.
-Requires simple device to host and integrates perfectly with the internet.
-Has a great collection library to edit your work.
-Offers pocket-friendly cost to all users.

Cons

Not all our needs were met with ease following the great expectation that we had. Here are some points to have in mind even after the great ability has been demonstrated.

-It works with predefined command.
-Requires strict monitoring as changes can be compromised to interfere with the meaning.
-Fast and stable internet is a must have for success.
-You need technical know-how to manipulate and make changes on the platform.

Pros

Git hub gives you options to manage your code. I like that I can use the command line to interact with git, but I can also use the GitHub desktop application, or the plugin for my IDE of choice: Atom, or the plugin for my colleagues' IDE of choice: VS Code, or any number of other apps.
The pull request merge workflow is also wonderful in that it allows code inspection and comparison.
Minor edits can even be made on the GitHub website and will become part of the regular git history.
GitHub actions allow us to do things like run unit tests and check a test build before approving code for merging to the main branch.
My absolute favorite part about GitHub is that it allows me to collaborate and contribute to projects that are not directly under my organization's control, but part of the open source community.

Cons

Honestly, there is not much I dislike about GitHub. My biggest complaints about it are more related to the choices my organization has made around using GitHub. I would like to use GitHub for issue tracking and project management, but we have contracts with other paid tools that offer roughly the same functionality.

If I had one request for a better user experience it would be to improve the quality and capability to search for code within a specific repository. The feature exists, but it feels primitive and very basic. I want to be able to search through version history and have better search matches (instead of fuzzy matches). Better search tools would make GitHub even more useful.

Pros

Free service, while there are also premium options, a Large community, quick searches inside the structure of the repo, and accessibility to support.
With GitHub, you may store your projects and make them available to your colleagues for inspiration or collaboration. The beauty of it is that you can have many people work together remotely on a project, putting you all, so to speak, on the same page.
With GitHub, you may store your projects and make them available to your colleagues for inspiration or collaboration. The beauty of it is that you can have many people work together remotely on a project, putting you all, so to speak, on the same page.

Since Microsoft acquired GitHub, we are now able to host private projects, and they will function with any CI environment, including CircleCI or GitHub.

The most well-known git implementation is GitHub. GitHub provides a wealth of reliable information about source code contributions for security evaluations. Both the command line and the GUI make it simple to search for new source code changes, making it simpler to find modifications and potentially susceptible code. Additionally, it is simple to comprehend what changes were made to the source code following a security update, making it simple to grasp how they were implemented.

Cons

It isn't completely open because you aren't allowed to upload anything larger than 100MB and the free version's repository size is just 1GB.
Getting used to the mental model when you're new to GitHub is one of the difficulties that is frequently mentioned but becomes easier over time and with experience.
It might not be the ideal instrument for documenting ideas or the creative process. LayerVault or a program that is comparable to it would be a fantastic choice for this particular task. Git, in our opinion, is not the ideal tool for tracking design but is quite effective for tracking code. When drawings must be converted into code or exported to a production environment, it might appear to be a little bit of a murky area.
I'd love to see GitHub release a feature-rich mobile app to make managing repositories on tiny screen devices easier and more practical. This would be necessary for developer workflows that need problems or work-item capabilities.

Pros

i found the following features as most impactful:
- version controlling
- dependabot for vulnerability scanning
- integrates well with third-party based app
- ability to go back to previous versions if present code shows error
- high repository privacy
Yes the product is quite easy to use for:
- hassle free source code hosting
- Container Registry quite helpful
- open-source community involvement fostering
- user interface is really smooth easy and Excellent
- open-source applications/code of all available to tweak
Yes i was successfully able to implement the integration of the app/software/SAAS with my existing business processes quite smoothly and easily as i could set it up with a little self-help, effort, and online training guides..

Cons

I found the following features that were either missing or could be improved:
- merger-conflicts through github could be improved
- pull request codeview could be improved
- no options for delete update and issues create for teams and users
- Like many other IDEs, the code editing environment features lacks in additional functionalities.

I found the following features or aspects of the product that are difficult to use:
- folder deletion
- absence of rich CI/CD
-one is  unable to install, download, as well as set up one's own GitHub server.
- permanent removal of unwanted files
- misleading repository contributions count
No, the integration of the app/software/SAAS with my existing business processes not so much difficult as i could set it up with a little self-help, effort, and online training guides.

Pros

Github has significantly altered the way I approach software development projects; I've been using it for a while now. It has been incredibly simple to collaborate with other developers and keep track of my code thanks to the version control feature. The tools for code review and issue tracking are particularly helpful because they make it simple to keep track of any bugs or adjustments that need to be made. Github also has a lot going for it in terms of open-source development. Numerous open-source projects have allowed me to participate and utilize them, and the supportive and welcoming community is always there to help. Building my portfolio and showcasing my work to potential employers has also been a great benefit. The ability to integrate with my continuous integration and deployment services, for example, was made possible by Github's integrations with other tools. I can manage the permissions of my project contributors with ease thanks to the access control feature. I also enjoy having access to my code from any location, and the remote backup feature gives me great peace of mind. I've looked over other developers' code on Github and contributed to their projects as a way to learn. All things considered, Github has become a crucial tool in my workflow, and I can't even imagine doing software development projects without it.

Cons

I've been using Github for a while, and while it has some great features, there are a few drawbacks as well that I've found annoying. First off, the price can be a little high, especially for private repositories or big teams. Larger projects may encounter difficulties due to the free plan's constrained storage. The navigation and interface can occasionally be a little bit perplexing to me. New users may find it overwhelming, and the customization options are few. Additionally, I've observed that some languages don't offer as strong support for code review and syntax highlighting tools. Github also doesn't seem to be designed for large enterprises, and it might not have the scalability options they require. Additionally, the fact that it is reliant on the service's uptime is somewhat of a drawback. Additionally, I discover that Github has a small number of integrations and that I am unable to locate the precise tools I require. Additionally, I don't have a lot of control over my privacy and data. Last but not least, I discover that it lacks integrated project management features, forcing me to rely on third-party tools. Although Github is a fantastic tool overall, some users may find its limitations to be infuriating.

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.

Pros

It is very easy to collaborate and work on code changes, publish releases, and run automation scripts. The UI is fast and they are improving it constantly making it quick and efficient to navigate to the repository and even the file you want.

Cons

My biggest gripe about GitHub is the billing. You have to buy a fixed number of seats and you can only increment it in 10s. So, even if you need just one extra user, you still have to pay for 10. It also takes a long time (2-3 days, more in some cases) to get the licenses added. I can't even process why this is the case. I would much rather have preferred usage billing.

Alternatives Considered

Switched From

Pros

1.Robust task management: GitHub's task management system offers a comprehensive set of features that make organizing, tracking, and prioritizing tasks a breeze.2.Seamless multi-project management: GitHub excels in handling multiple projects simultaneously, allowing users to effortlessly navigate between projects and keep everything neatly organized.3.Powerful collaboration capabilities: GitHub fosters real-time communication and efficient collaboration among team members, with features like commenting, suggesting changes, and reviewing pull requests.4.Integration with popular tools: GitHub integrates smoothly with other widely used project management tools such as Jira and Trello, enhancing its versatility and compatibility.5.Version control excellence: GitHub's version control system ensures that everyone is working on the latest version of the project, minimizing errors and conflicts while maintaining a seamless workflow.6.Intuitive user interface: GitHub boasts a clean, well-organized interface that is easy to navigate, making it accessible for users of varying technical expertise.

Cons

GitHub's features and functionality work together harmoniously, ultimately boosting productivity and enabling employees to achieve their project goals efficiently.

Pros

GitHub provides a single service where source code control, documentation, issue tracking, and more are possible. All of these aspects are well integrated and can even reference lines from the source from different commits. Pricing for academics is extremely generous.

Cons

There's not much to not like in GitHub. It does a lot of things well. Some little things can be improved like better user administration and creating a way for users to sign-up for your organization rather than inviting a user to join your organization.

Pros

As a platform for version control, it offers an intuitive and user-friendly interface that makes it easy for developers to collaborate on code, track changes, and manage multiple versions of a project.One of the important strengths of GitHub is its vast community of developers. GitHub provides a wealth of resources for developers looking to learn from others or share their own work with the world. This community also provides a platform for collaboration, allowing developers to contribute to open source projects, participate in discussions, and learn from one another.In addition to its powerful version control features, GitHub also offers a range of tools to help developers manage their projects. These include project management tools like Kanban boards and issue tracking, as well as integrations with other popular development tools like JIRA and Trello.Perhaps the greatest strength of GitHub, however, is its commitment to open source development. By providing a platform for developers to share their work with the world, GitHub has helped to democratize software development and empower developers of all skill levels to contribute to the larger community.

Cons

One of the biggest issues with GitHub is that it is very hard to learn how to use it at first. No novice developers, the tool can be overwhelming. A lot of features in GitHub requires a thorough understanding of coding and software development. Another disadvantage of GitHub is that for technical users, the free version is limited. The paid version is definitely recommended; however, small groups might find it on the expensive side.

Pros

Version control: GitHub provides a powerful version control system that allows developers to manage and track changes to their code over time.Collaboration: GitHub provides a range of collaboration tools, including pull requests, code reviews, and discussion forums, that make it easier for teams to work together on projects.Open-source community: GitHub is home to a large and active open-source community, making it easy for developers to find and contribute to projects, as well as access a wealth of resources and support.Integrations: GitHub integrates with a wide range of tools and services, including popular integrated development environments (IDEs), issue trackers, and continuous integration/continuous deployment (CI/CD) systems.Security: GitHub provides a range of security features, including two-factor authentication, encrypted communication, and the ability to encrypt sensitive data at rest.Large repository: GitHub hosts a massive repository of open-source projects, making it easier for developers to find and reuse code, as well as contribute their own projects to the community.Ease of use: GitHub has a user-friendly interface and is designed to be accessible to developers of all skill levels, making it easy for users to get started with version control and collaboration

Cons

Limited customization options: While GitHub provides a range of features and capabilities, some users may find that the customization options are limited, particularly for advanced users.Cost: For larger organizations or enterprises with many users, the cost of a GitHub Enterprise subscription can add up over time.Performance: Performance issues can arise when working with large repositories, particularly when many users are making changes at the same time.UI limitations: Some users may find the GitHub interface to be limited or confusing, and may prefer to use alternative Git clients or GUIs.Limited issue tracking: While GitHub provides basic issue tracking capabilities, some users may find that these are limited and prefer to use alternative issue tracking software.It's important to keep in mind that the limitations or drawbacks of GitHub may vary depending on the specific needs and requirements of the individual or organization. It's recommended to carefully evaluate their needs and compare the features offered by different platforms before making a decision.

Pros

Github has a large community of developers contributing to various open source projects. It has a fantastic user inteface that is easy to use and navigate. Github offers plenty of tools and resources available for collaboration, version control and CI/CD.

Cons

Some features may be overwhelming for beginner users.

Alternatives Considered

Switched From

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

VCS and it's being free for all basic needs, from the smallest firms to IT behemoths, everyone uses GitHub.

Cons

the learning curve may seem steep if someone wants to do advance pull requests and forking.

Alternatives Considered

Reasons for Choosing GitHub

Reasons for Switching to GitHub

Pros

The entire code versioning tool is so easy to use and does every branch operation with visual clarity. It implements git quite easily, especially with a RSA key.

Cons

There is no real issue with GitHub. It does exactly what it is supposed to be doing. I could say that I had a few difficulties learning the concept of versioning when first using it.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

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

Reasons for Switching to GitHub

Pros

Starting with versioning, ease of code management & collaboration, which is of utmost priority for any company that wants to develop code. GitHub provides it all.
They keep adding new features such as vulnerability scanning & integrations with IDE platforms like VScode. This makes GitHub even more reliable & convenient for coders.
Today, majority of coders will tell you to choose GitHub over any other platform given how much it has helped them & their company to develop code, continued with feature & bug management.

Cons

Merge conflict handling has improved since it was first implemented but there is still a lot of scope to make it easy for developers.
Code search is another feature I want GitHub to improve on, currently it does not allow to search for specific piece of logic inside a big repository until you take a pull & do it in your IDE

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

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

It's very easy to integrate with other software that the company already use it. For example, we use Discord to communicate between coworkers, and thanks to the Github bot integrated in it, there's a message each time someone approved a Pull request or Closed an important Issue. Also, with his integrated CI/CD, we can now upload a new version of the app and even testing it, so the final user can have a very good experience without major flaws.

Cons

I wish that Github can have a better use to link Issues and Pull Requests, it's very interactive but there are time that I forget to link some Issue and it's a little frustrating to have some unlinked Issues after a sprint.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

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

Pros

Setting up and getting started with Github is quite simple. When you begin a new repository, you will be guided through the process of effortlessly adding your source code from your computer to your repository using a few simple instructions. It also has a large number of other capabilities, such as task management, problem management, interaction with DevOps for deployment, static hosting of websites, and a great deal of more functionality. Additionally, it has a high level of extendability and enables you to integrate a large number of market-sourced components. You have the option of keeping your source code private or making it available to the public.

Cons

Some time for me Because GitHub was developed without a simple user interface, verifying even the smallest and easiest things, such as a date, requires you to hover over another date in order to give you the exact hour and time of a commit per se. Because of things like these, using GitHub may be challenging for those who are just starting out with the program, but it becomes easier the more you work with it.

Alternatives Considered

Reasons for Switching to GitHub

Pros

There are several aspects that I like about GitHub as a software developer, having this high potential tool at hand makes it much easier to carry out projects of great value, since in one place it is possible to carry out the entire process necessary for a clean code.I like that it allows to be able to manage in a more reasonable way the time of development of versions and the time that is needed for the review of the code, because by being able to allow access to whoever you want to be able to solve any problem in the code, it makes it easier for them to solved in the shortest possible time. Not only does it guarantee a clean code but it also allows synchronizing the development of the code, that is, different tasks can be assigned to several members so that the progress of the project is rapid. A valuable feature of this tool is that it makes it possible to get the original code and even make changes without having to worry that the other team members will not have the updated version, this saves time and avoids overwriting the code which can be a great benefit error. In addition, assigning tasks allows the project to be much more fluid and that the workflow does not fall on a single person and the best thing is that it is simple to track progress. For example, assigning tasks gives me and my team to have better coordination and be able to advance in each task quickly.

Cons

GitHub is an ideal tool for developers and programmers and even students since it allows you to work in private or public repositories, being able to interact with other developers, however, before being able to use each of its functions smoothly, you need time to fully understand it said software, this is because its learning curve can be somewhat high and more so if you are a beginner.

Pros

- The most important feature that we use at a very critical phase is the version control, creating pull requests for the developers to review the code base continuously, for continuous integration and continuous deployments for merging code and deploying code to production
- The tool is very easy to use and navigate without any prior experience
- The tool has very good support team to resolve any issues in the process
- The tool is very widely used by enterprise companies in the market to manage the code base

Cons

- The pricing could be more reasonable as compared to the other tools in the market
- The UI can be more intuitive for the users to work with
- The tool can include more features in the tool that could be used by many customers instead of building custom API's and having issues in the workflows.

Alternatives Considered

Reasons for Switching to GitHub

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

Reasons for Switching to GitHub

Pros

Administrator takes your code and changes it into a powerful, dispersed pipeline. You can keep on utilizing your current devices, dialects, foundation, and contents.

Official forms a rich DAG structure, however such that regards positive designing and doesn't repress it. You can utilize Prefect's useful API to change scripts with insignificant snares; or you can get to the conceded computational diagram straightforwardly; or any blend thereof. It depends on you.

Cons

GitHub is dead-easy to use in the fundamental list of capabilities. The arrangement is negligible and all forming observes guidelines and so forth We had no issues setting up access for different clients and when private archives opened up even in the complementary plan it was an easy decision.

Githubs Actions region large assistance - when set up appropriately and can assist with computerizing errands like sending more than a few servers. It is an exceptionally useful asset, however perhaps more convoluted to arrangement then in other comparative products.

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

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

GitHub is dead-simple to use in the basic feature set. The setup is minimal and all versioning follows standards etc. We had no issues setting up access for other users and once private repositories became available even in the free tier it was a no-brainer.
Githubs Actions area big help - when set up properly and can help automate tasks such as deployment over several servers. It is a very powerful tool, but maybe more complicated to setup then in other similar produts.

Cons

The product management additions seemed as a good idea first, but rendered unusable (for us) since it people (devs) tend to use one app for versioning in command line and other apps for tracking and reporting. Comically joining them was not well received.
The GitHub desktop app can cause authentification issues for non experienced users.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

When you think about source code management you'd think of GitHub straight away. The security is taken seriously on GitHub and the CLI has made using it super simple and convenient from the comfort of your terminal. The offering of integrations with different DevOps tools is a must-have these days that you'd get out of the box with GitHub. Another important factor that makes GitHub stand out is its reliability which in the entire time that I've used it has always been available and has never been down.
GitHub has not stopped innovating new features and improving their services after all these years and it's amazing to see that they offer a new feature frequently.

Cons

I'd love to see a feature-rich mobile app from GitHub to allow managing the repositories easier and more practical on small screen devices.

Alternatives Considered

Reasons for Switching to GitHub

Pros

I've been using GitHub for more than 10 years. It is the goto hosted Git service for my personal and enterprise SCM platform. It has pretty much everything you need for software development starting from source code management to issue tracking, project management, build tools (Actions) and online code editor. I also use GitHub CoPilot which is great productivity tool saving at least 30% of my development time every day.

Cons

There are no complains really! I love everything about GitHub.

Alternatives Considered

Reasons for Choosing GitHub

Switched From

Reasons for Switching to GitHub

Pros

GitHub is the industry default for code management with Git. If you use Git, you probably already know and use GitHub to keep your various repos safe and in the cloud. It integrates with absolutely every DevOps tool and system under the sun. And probably also the text editor you are working in. And probably also the communication tool you are using -- Jira, Slack, whatever. All of them talk to GitHub. Its help pages are the best in the business too. And it seemingly never goes down. We depend on it the way we depend upon electricity being in the wall socket.

Cons

Unfortunately, the UI on GitHub is far from ideal. I use GH every single day, yet I still often find myself struggling to figure out where to find what I KNOW is in there. The Go to File button -- not sure why that is always hard to find. How to pull up a list of all the commits for a particular branch? Why is it that tiny little 'commits' button? It's like there are 3 or 4 different subnavs on the site -- each of which has its own logic, but it's not intuitive which one you should be looking at to figure out what you're supposed to be clicking on. It feels like somebody with real UI chops could figure out how to help GitHub take all the awesome features they have unleashed and put them into a more sensible layout. I hate feeling stupid, yet I often do when looking to find something in GH.

Alternatives Considered

Reasons for Choosing GitHub

Reasons for Switching to GitHub

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.