GitHub Reviews

We used GitHub to host our open code, to publish our site with GitHub pages, and to find open code plugins and open code software utils. We also used GitHub to contribute to 3rd party code.

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.

GitHub is our primary repository for all the code in the company. GitHub also serves as the main integration point with other pieces of software, including integration into continuous integration and continuous deployment services.

GItHub is being used as the main repository for version controlling all of our software. It provides a safe house and central location for storage as well as facilitates permissions for accessibility.

We currently use GitHub to put in request for IT work to be fixed. We have 3 out of 5 employees using GitHub. It speeds up the process of getting things done faster and not having to go through multiple steps. It has really helped!

We use GitHub to host all of our public repos, and several of the private repos for our organization. It does the job well, developers are familiar with it, and the price is reasonable. We have no complaints, but we also haven't seriously evaluated alternatives. We don't really use the issue tracking features so our use of GitHub is pretty limited, but the importance of a hosted repo solution cannot be understated.

All the members of my research team, who are members of various departments, use GitHub for version control. Besides version control for code, we also use GitHub to write collaborative papers and store important code from previous research projects. Developing code as a team is incredibly difficult without good version control software. Fortunately, GitHub facilitates this process by making it easy to reconcile conflicting versions of code or reports. Furthermore, 'branching' makes it easy for several people to work on different sections of a project without affecting the main project. The changes made on 'branches' can later be merged back into the overall project. Since most of the members of my research team are in different buildings within our organization and in different states, GitHub also allows us to all work remotely on code as a team. GitHub avoids the inefficiencies that result from emailing reports to team members and having to merge track changes. Finally, GitHub acts like a back-up tool, which is incredibly useful. GitHub makes it easy to revert back to a previous version of a project, because it saves the changes that are made by team members on a timeline. Overall, GitHub has made our code development much more efficient and saves us a lot of time and hassle!

Github is very easy to use git hosting provider server. Github allows easy contributions of code between our project members. Github provides a way to review code before it is merged into master branch. It provides a nice interface to view all commit history and allows to easily compare two different commits. Github provides fast searching across all files. I recommend GitHub to all developers who are looking for a simple and easy to use source code management and git version control hosting server. GitHub has some of the best documentation around. Github makes easy to contributions to projects within small and large teams.

As a technical recruiter, I use GitHub to identify users of the site who are skilled in specific technologies. For example - if there is a discussion about using microservices to break down a big ball of mud, I would then start looking at the profiles of developers who seem to have expertise in this area. It's especially helpful when recruiting for developers - just because someone codes in Java, doesn't mean they're a fit for a Java Developer role - it's about what they've done in Java. Github helps me discover WHAT they've done - not just what language they've used.

GitHub is currently used by I entire organization to fork and customize popular repositories for our company's own usage. We additionally privately host our own original code repositories. GitHub has many useful integrations that work well with our company's choice of products for productivity, management, etc... and allows for easy, quick setup when there isn't a lot of time for overhead.

Our organization currently uses GitHub as a platform to collaborate with our remote developers on the new website that is in the works. Only the IT/Web Development team is using GitHub, the other employees would have no use for this platform. A major business problem GitHub solves is the ability to share code with our remote developers with efficient version control for editing.

It's being used by a few departments within the organization. Different groups used it to varying degrees. Of course, it was used as a version control system, but other groups (like the one I was a part of) also used it for CI/CD purposes. I think this is where GitHub really starts to shine. It's definitely useful just as a Git repository, and we would gain a lot from that. But what brings it over the top is its integration with a lot of other tools we used, including Slack, Jenkins, and custom integrations utilizing webhooks. This allowed us to use GitHub as a central repository, not just for code, but also for knowledge, interactions, auditing, etc.

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.

The entire engineering and product organization has logins to GitHub and uses it to develop all of our software and even some of our processes (through Wikis). The big problem it solves is source control centralization for the organization, with the largest use case being code pull requests for all new code that goes into production.

We are using Github within our software research and development department as our software versioning system. We have our codebase available in multiple projects on GitHub and continuously make adjustments to it using Git branches, merge requests and tags. Our team also reviews new merge requests within Github. With this, we are able to have a history of our code, so we can always revert back to an earlier point in time.

GitHub is a great solution to have version control in your application, I think that for any programming team it is essential to have this type of tool, it is essential since you can have your project in the cloud and you can define work teams for projects, define security options by project and give access to the code to your collaborators, it also solves many problems with clients since you can configure several deployment environments and versions of your application so the client can have an idea of how the implementation of your application is going . This is a tool that is always present in the IT development teams.

I was a technical project manager for a big automotive client. My role was to create educational simulations for automotive technicians. In doing so, I played a team leader role in storing repositories/source code for each of the projects that I manage. We were concerned about longevity, security and management of code and GitHub addressed all of the above.

Git is one of the best distributed version control tools I've ever used. GiHub makes it easier to use Git from a Graphical Interface. It is widely used across all the platforms in our organization. It unifies and maintains the code repository from different developers. We deploy the code to production from our centralized GitHub repository.

I've used github for side projects and hosting a company wordpress theme for a few years. On a personal level, github is great for saving projects and showcasing the different languages you are proficient in. We use it for our platform and to make sure we have a place to review our code as a team. I use it in each and every project so that i can always look back and track progress, or roll back incase I break something. If you aren't using git in some form on a project, you leave yourself vulnerable to mistakes.

My companies use github for collaboration. It makes it really easy to keep everyone on the same page, even if they're working across the world! We have people in Los Angeles, Phoenix, Chicago and London all working together through programming and project management tools included inside github!

I use GitHub as my source control service. I can easily track the code change, branch the projects, and go back to the previous change. It can also share the project files, collaborate with others, and showcase my coding experience. Also, I can get open source codes from other developers to use and to modify for new projects.

GitHub is being used for the engineering group’s - primarily for software engineering and some DevOps scripts.

As we build open source projects, GitHub is the best place to welcome contributions from the outside but also manage processes internally better. We have best practices to not merge our own Pull Requests and review those of others before merging, we use GitHub in conjunction with other managing tools which use GitHub to track progress, including Milestones and Epics to categorize issues better.

GitHub was used a previous place of employment of mine. It was used by several developers who wanted easy and fast access to the repository. It made it really easy to control our code base.

It is the first place I look to use as a code repository on any project I am on. No more worrying about what would happen to your code if your computer dies, it is on GitHub. Collaboration with other developers via GitHub is a great experience.