GitHub Reviews

I mostly use GitHub to save repositories that I encounter when scrolling or searching for resources. Even if they are not immediately relevant to me, I know they will be useful in the future. So, I save those repositories in my GitHub account. Whenever there is any requirement from a client or a project with a similar base, I use those repositories for the data.

GitHub has made handling repositories more manageable and helps in organizing resources effectively.

The most valuable features are the speed, low latency, and the clear, concise set of commands. GitHub is not complicated to use and is very user-friendly. It's also beginner-friendly, making it welcoming for newcomers.

There is nothing that I find that needs improvement in GitHub. The introduction of GitHub Copilot has made everything much easier and flexible.

I have been using GitHub for around two years.

GitHub is a stable product. There are no issues with stability.

I have never needed to contact GitHub's support team. I have always found alternative solutions if I encountered any issues.

Positive

If you do not have any dependencies installed and you are starting from scratch, it takes about 20 to 25 minutes to ensure everything is according to your needs. While installing other dependencies and tools, GitHub can also be installed, so it does not require extra time.

The pricing is reasonable and not expensive.

I would recommend GitHub to others as it is user-friendly and easy for beginners to adapt to and learn. The introduction of GitHub Copilot has further simplified usage.

I'd rate the solution nine out of ten.

I use it for repositories. We use it for version control and for deployments. We use pipelines in GitHub to deploy projects in Salesforce.

GitHub is much better than similar tools like Bitbucket. It's cheaper, and resolving merge conflicts is much easier.

In complex cases, we have to use the terminal for conflict resolution. If those conflicts could be resolved visually in the editor, that would be much better.

I have been using it 

It is a stable product. I haven't encountered any bugs in the last few months.

It is a scalable product. Every developer in my company uses GitHub, so if my company has 100 developers, then 100 of them are using it.

The initial setup is very easy. 

It's cheaper than Bitbucket. Bitbucket is more expensive in terms of pipelines, which charge based on the time on the Python page in streaming.

I would recommend using it. It eliminates a lot of hassle. For example, suppose you're assigned multiple tasks. You could be working on one task and commit changes to a development branch. If something else becomes a priority, you can switch to that task and commit changes for it. This way, you have backups and can control the versions of your product.

It's beneficial for managing multiple tasks and controlling versions of your product. 

You can commit changes to branches for development, and if something is a priority, you can switch to another task and commit changes for that. 

GitHub provides a backup and allows you to control the versions of your product.

It is easy to learn. I would rate it a ten out of ten. 

You can write the code with AI. But when it comes to implementation, you must upgrade the bits of code that will support this and generate solutions based on that architecture. Then, you need comparable code bits. Therefore, AI can propose how much a specific function can be better optimized. So, AI can help stakeholders reach tasks quicker.

I decided not to use GitHub but developed my tool because I found it more efficient. I'm familiar with my tools, making them easier to use. I like being able to customize them to fit my workflow and the way I think.. Software development is like a personal workshop, and I tailor my version control to match my approach. 

You have to do the crazy things to make real changes. Everything stays the same without them. Having a good backup system is crucial. If something goes wrong, you can roll back to a stable state. This mindset drives me to create tools that align with my thinking. These methods aren't easily accommodated on platforms like GitHub, so I prefer to use my tools. 

The solution is the priority, not the specific tools or methods used. For example, imagine you need a simple solution, like a pizza kiosk locator. You're driving and want to find a pizza place quickly. The solution should focus on delivering this functionality, perhaps using Google Maps integration. The key is prioritizing the solution over the technical components.

The solution should allow you to press a button, see the distance to the nearest pizza place, navigate there easily, and even contact them if needed. Companies have resources and processes. The key lies in leveraging these resources to enhance business processes and stay competitive. The primary focus should always be improving efficiency and competitiveness through better combinations and evolution of these processes.

Despite its age, GitHub still holds value, especially in its older functions. However, to maintain relevance and satisfy existing and new users, GitHub should develop newer functions while preserving its traditional ones. This balance would ensure the community's satisfaction and integrate newer features. It seems they're already aware of this need and are working on it, so it's reasonable to expect gradual improvements over time.

The tool is scalable. 

GitHub has become a standard in software development, with millions of users, solutions, and a vast array of software packages and commits. It's reliable, proven, and fosters a strong social community. However, it's important to recognize that not all development processes fit within the GitHub model. In some cases, like ours, we have a unique setup where certain components, like front end and JavaScript libraries, can be hosted on GitHub, while others, like the database, are better managed internally with our tools.

Many solutions are inherently vendor-specific because they reflect the unique way each company conducts its business. These processes often give companies a competitive edge, and they're closely guarded as proprietary secrets. Exposing these processes to a wider audience could diminish that competitive advantage.

Lufthansa, for instance, relies on around ten thousand applications developed in-house and with partners to run their core business operations. 

Similarly, as a competitor in Formula One racing, Ferrari undoubtedly has closely guarded secrets contributing to its success.

SAP encountered issues with its approach to creating minimal solutions for small and medium-sized businesses (SMBs). While they intended to cater to smaller companies, cutting functions led to a loss of value, making it no longer truly SAP. Similarly, many large companies adopting out-of-the-box SAP solutions found their processes becoming standardized, causing dissatisfaction. Companies wanted their unique processes preserved, not homogenized like competitors'.

I rate the overall product an eight out of ten. 

I use GitHub for version controlling of the code. I have experience using GitHub to upload the source code and manage tasks.

GitHub has improved efficiency by being easy to use for any user, and it offers good documentation that makes it easy to follow the steps.

GitHub provides enough storage for uploading the source code. It makes it easy to push code, and the Git commands are straightforward to use. The documentation is also good, and I appreciate the CI/CD pipelines that we use for web applications to upload the application in development mode and production mode.

When I was new, I faced challenges with Git commands, such as reversing or deleting mistakes. Additionally, merging code from multiple branches can sometimes result in conflicts, which are difficult to resolve.

I have been using GitHub for five years.

I have not faced any issues with the stability of GitHub.

For large-scale projects, there can be issues when multiple employees work on the same project and need to merge code into a single branch, resulting in potential conflicts. However, it's a problem with team understanding, not GitHub itself.

GitHub's support team is really good.

Positive

I used GetStream.io earlier, but I have not implemented it in a live application.

I do not know anything about the pricing.

I would recommend GitHub to my colleagues.

I'd rate the solution ten out of ten.

One major disadvantage, which I believe GitHub is and which the tool should work on, is that it does not provide good reporting capabilities from a compliance perspective. If we are using GitHub for 500 users, sometimes the compliance team asks for a certain kind of report on how many users are not active and who left the company, and GitHub does not provide such a granular report. GitHub should improve its reporting capability.

GitHub should work on enhancing its search capability. The tool should add some more features and functionalities.

I have been using GitHub for six to seven years.

Performance-wise, if we have set it up properly, we will not encounter any major performance issues with the tool. It works fine.

My company has an enterprise-level setup, so we have a large user base.

The technical support of the solution is good, and our company has used it for GitHub upgrades. We raised our tickets with the support team. Support-wise, GitHub is good. They respond back on time and give us the exact SOP, which we need to follow when we run into some specific issue where we need their support. Support-wise, they are good. I rate the technical support an eight out of ten.

Positive

Some other teams in my company use GitHub Actions.

The product's initial setup phase is straightforward. It is not very difficult. In our company, we have a setup on the server and on AWS also. We are using the cloud version of GitHub.

The tool's pricing was compatible with our company's needs. As far as other tools are concerned, I think, in terms of price, GitHub is okay compared to other tools.

Before GitHub, we used Perforce and some other products as source code management tools. GitHub is more agile-centric and flexible than other tools. GitHub is better accepted as a source code management tool, and that is the reason we are also using it in our company.

My company started to use GitHub as it is well-integrated with other tools and as it provides better support. Suppose you go into some issue or something like that. GitHub's support structure is better, allowing you to do more hit-and-test on the solutions than other tools. With GitHub as a tool, if you run into some issues, you get a lot of articles over the internet. Support-wise, GitHub is a better tool.

GitHub provides you with code-scanning capabilities. If we are using GitHub for CI/CD, it does provide such capabilities. From the code review point, it provides us with a feature to protect our branches and all that. It provides us the feature to help decide who can push to the repository or how many levels of reviews are required. I think these tools should work more on branching. In the branching area, the tool should provide a bit more flexibility.

My company has a couple of AI-driven projects managed with the tool.

The tool is not difficult to maintain.

GitHub is more development-centric and agile-centric, and it integrates with all our CI/CD tools and other things. The tool helps across the project teams to get things automated, and it helps in the quality review process, so eventually, it helps in quality delivery.

.

If some organization wants to go ahead with GitHub, there are definitely no cons or anything for which you will say that business units or companies would not go ahead with it.

I rate the tool an eight out of ten.

We use GitHub to track what kind of libraries you are using.

The most valuable feature of the solution is the version control field. GitHub has a good integration and coding engine.

It would be beneficial if GitHub provided some security scanning for new libraries to ensure that there are no viruses in it. The solution’s stability could be a bit better.

I have been using GitHub for two months.

I rate the solution a seven out of ten for stability.

Around 30 users use the solution regularly in our organization, and we plan to increase the usage.

I have previously used Bitbucket.

The solution's implementation takes a long time.

We pay a licensing fee for GitHub, which could be cheaper.

The solution is deployed on the cloud in our organization. I would recommend the solution to other users. GitHub is a version control, and you can always switch and text because every version is saved.

Overall, I rate the solution a seven out of ten.

For GitHub, we host our app there, and the code is secured up there in GitHub. We have multiple projects built there. The code is in the GitHub cloud, and we use it as a storage bucket for our codebase that stores our multiple projects and repositories. We use GitHub Actions to automate workflows; whenever we add a new feature to the project or app, GitHub Actions automates testing, deployment, and checks best code practices.

GitHub makes the process really fast for delivering projects, especially when multiple teams are contributing to a single project. It reduces the hassle by having all contributions in a single repository.

GitHub is easy, secure, and widely documented. We use GitHub Actions and Workflows for performing tests and deploying services quickly. It's a well-documented platform with functionalities that other repo systems lack.

GitHub could automate the setup process more, such as creating YAML files for GitHub Actions. The mobile application could be more useful, providing updates on iPhones or Android phones. There could be enhancements to automate branch deployments and other setups.

Currently, I'm working with GitHub. It's been about six years.

GitHub is super convenient and stable, which contributes to its popularity.

GitHub is scalable; I have worked on solutions with tons of features and thousands of branches in a single repository without any glitches.

I have worked with Bitbucket. Bitbucket is useful for creating private repositories, but GitHub is more convenient and vastly documented. It is more widely used and established as a standard.

The initial setup of GitHub is very straightforward and well documented. Even if someone is new to it, they can easily find guidance from online resources.

I have used Bitbucket as well.

While creating repositories, it's important to read all the documentation, especially when setting permissions or creating tokens. Missteps can create problems.

I'd rate the solution ten out of ten.

GitHub is used to maintain code in a centralized place, which allows multiple teams to work on the same repository. It is also integrated with Jira and other tools like CACD pipelines. GitHub streamlines project collaboration by enabling developers to clone, modify, and push changes into a centralized repo. It supports project collaboration for software development processes.

GitHub aids in distributing work among team members, allowing them to focus on their own tasks without worrying about conflicts. By integrating with Jira, it helps track the progress of tasks and their states, such as development, merge, or deployment. It provides a secure and reliable way to store business code.

The most valuable features of GitHub include its ability to integrate with Jira and multiple CI/CD platforms like Techton, allowing for seamless project management. Additionally, the pull request feature, which controls code insertion into branches by code owners, is highly beneficial.

GitHub could improve in resolving conflicts when multiple developers modify the same line of code. Introducing a feature to manage and resolve conflicts directly within the application rather than on local machines would be beneficial.

I have been using GitHub for four years.

GitHub is stable, as I have never encountered or heard of issues such as application crashes or data loss. Even if server issues occur, GitHub takes responsibility, ensuring stability.

As an intermediate-level user, I find GitHub's scalability to be high, rating it at nine out of ten. Its advanced features allow maintaining multiple projects effectively.

I don't have any experience with technical support for GitHub.

Positive

Previously, I used GitLab, which has its own pipeline features. GitHub was chosen for its maturity, reliability, and global adoption by many organizations for application development.

GitHub is easy to set up, rated ten out of ten. Users just need to set up a username, password, and create an access token. It is user-friendly even with basic knowledge, and the GitHub official page offers simple documentation.

Each individual is responsible for maintaining their repository. GitHub management and maintenance are handled by all project team members collectively.

I have not paid for GitHub as I use the free version for personal projects. Organizations may take separate servers from GitHub based on their needs, yet I am unaware of the pricing details.

Users can trust GitHub as a secure place to store their business code because many large organizations use it. It provides a reliable centralized location for maintaining repositories, and its maturity and research make it a best-in-class option.

I'd rate the solution ten out of ten.