GitHub Reviews

We are using GitHub in our development team as our source control solution. GitHub allows us to easily work from either the office or remotely. Git's distributed version control makes branching incredibly easy, and GitHub provides the most seamless and easy to use Git solution I have found. GitHub provides a ton of integration options with any tool you are using.

The development department uses private GitHub organizations for version control of web applications and internal analytics programs. Only development uses it, the other departments do not create new code or interact with it so it's only been appropriate for us.

GitHub is our primary code repository for the company's web app. It allows us to effectively collaborate as a team on our codebase, while providing an easy system to track and manage changes. GitHub essentially serves as the Google Docs for our code. Specifically, it allows multiple software engineers to work on the same code in a separate environment that protects the primary codebase and is only merged in when it's working as expected. This allows for all kinds of collaboration, including with remote workers all over the world.

We're using GitHub for our entire software workflow cycle including code versioning, code review and approval, team collaboration on the code, and release management. Now, with actions, we're also building our Docker images and deploying them live, so it's a full CI/CD pipeline for us, all in a single package that's used by the entire development team.

GitHub is used by some development teams across our large organization, including our small web team. It's used as a central code repository for storing our website code and allows multiple developers to work on separate branches simultaneously, then merge those changes into the main branch once their work is finished. It also keeps a history of changes so we can tell who changed things and when they were changed.

GitHub is being used by the information technology department to work concurrently on projects we are looking to implement in the coming months. It addressed the issue of having to work together and input code from various locations.

Github is being used for version control and feature branches for our main website. The tech team is the only person with access to push or pull from the repository. Our industry is changing very rapidly, and so, the tech team is charged with adjusting our front-facing website hourly, and sometimes this causes conflicts when one of the team members is also doing a similar task. Thus, GitHub allows us all to stay in tune and be in perfect unison when it comes to deploying code out to the web.

Our design and development team uses GitHub. About 10 years ago we used to use SVN instead of Git and we tried some cloud services for hosted SVN repositories. At the time we felt that Git was more focused specifically on open source software projects, didn't have GUI clients for designers, and didn't have the project management-oriented features that we wanted. That has completely changed since then, and now Git and GitHub specifically is the perfect solution for our team. GitHub helps us build great software, and integrates with many services we use to help us be more effective with a distributed team.

GitHub currently isn't the main product we use for hosting our repositories. We primarily use Bitbucket currently and have plans to move to Azure DevOps whose repository hosting/management is re-skinned GitHub. My use of GitHub has primarily been working with open source libraries.

Git Hub is not used in any official capacity but there are numerous staff (developers), instructors and staff that use this industry-standard platform for sharing code and working collaboratively on websites and apps.

All our source code is hosted in private GitHub repos. All code reviews also go through GitHub and our deployment process goes through GitHub as well, pushing to the master branch triggers a GitHub webhook that deploys the code to production.

We use Github extensively for version control and team collaboration in all of our development/architecture projects. It's primarily used by our product team but we also use it to share information with the success team and collect feedback. Github assists us in the process of code reviews and is a powerful tool when managing/deploying multiple simultaneous projects.

We currently utilize GitHub as the default code repository host for clients who either don't have a current version control system or for internal projects that need hosting. It's primarily used across our whole delivery team, while projects from other departments may be hosted there as well.

Our department uses GitHub as its dedicated private repository for our production-facing web applications. In general, GitHub is popular across our organization (a public university), especially for students. GitHub gives us a high-quality, secure, cloud-based Git repository system at no cost, allowing our team to safely store application code, and to pull updates to our test and production environments, with minimal effort.

GitHub provides us with access to open source software and small scripts of code that we can use instead of writing the code ourselves. Knowing that the code is critiqued and improved by other developers and generally follows best practices, this allows us to analyze it's suitability and compatibility quickly. GitHub provides logs of the changes to this software to assist in bug finding and allows us to contribute to the software if we require a change.

GitHub is primarily for managing software source control, issue tracking, developer collaboration, CI/CD. We use it for source control, peer review, and server-side merge, CI/CD capabilities like automated test suite running for PRs and merges. We use a separate issue tracking system, but for many projects GitHub's built-in issue system is adequate, it has advantages like automatic issue references and linking of issues to commits, PRs. GitHub also offers wiki pages per project, team organization, and one of my favorites is its free static website hosting service called (GH-pages). Their static hosting is capable of consuming Jekyll (Ruby on Rails) based projects on the server-side. Open-source repositories and organizations are free of charge with a 1GB limit per repo. A limited number of private repositories for individuals (not organizations) are also free. GitHub can perform security checks of the packages used by the project and even propose recommended fixes to those in the form of generated PRs. Speaking of automated PRs GitHub offers extremely easy few click solutions to contribute bugfix PRs to open source projects and other actions can be performed solely using the web front-end.

GitHub is the most used tool in my team. I have been using this for a long time. I am really excited about committing updates to open source community and getting green commit dots on my profile as these green dots reflect your active time on GitHub. Every new update in our program, we commit to GitHub.

At our company, all Engineering and Product Design team members use GitHub. We use its code repository, version control, and ticket tracking tools to store, maintain, and manage code for various projects. It works incredibly well at all 3 functions and is an extremely vital tool for our entire organization.

After cloud migration, GitHub becomes obvious for use, especially its automation. The whole organization is using the GitHub as a hub. It works like a Repository where Developers, DBA, and QA keep their artifacts; and make them visible or accessible to the team. It works as a shareable location for the team. It works as the shareable location for all automate jobs. GitHub is a great Hub.

In our org, GitHub is not just used by developers but also by PMO teams to version control the documents which has a fabulous controlling which helps in maintaining the content of the files.

As per its flagship functionality of forking which is duplicating a vault starting with one client's record then onto the next - this empowers us to take an undertaking where we don't have compose access and change it under our own record. In the event that we make changes we'd like to share, we can send a warning called a "pull demand" to the first proprietor.

We use GitHub to host our code, back it up with source control, and as part of our software development life cycle via code reviews using the pull request feature. We also use GitHub to review the code of open source libraries and contribute to open source in general.

In my organization, GitHub is used by the development team, so everyone can keep track of the version control for the code we produce on a daily basis in projects.

It's used for managing source code primarily, and we use it to collaborate as a team across our various software projects. On a daily basis, our organization will use it for git source control. It's also used sporadically as a wiki, along with as an issue manager when needed. Though for most issue management, JIRA is used instead.

I use GitHub for personal projects to host my codebase for JavaScript-based web applications and projects used for learning different frameworks. It's one of the few major players between (others being Bitbucket and Gitlab). We don't use it at my day job because they only recently offered private repositories. We don't have open-source projects at my current company.

GitHub is the Version Control system used across the company by all the departments. It is hosted well within the company data center and every employee has a user created in the centralised GitHub. There are many organizations created for different projects/departments as per the need. Users can have both public and private repos in their own user profile. Though the user makes a public repo, it is still accessible only to people within the company as it is hosted inside datacenter and not accessible to open public. It is the recommended SCM across the whole company.