GitHub Reviews

We use GitHub for code repository alongside Bitbucket.

GitHub is very good for collaboration on software projects. We prefer Bitbucket for commercial use, while GitHub is used for open source.

My primary use case involves working with GitHub for code management. I have extensive experience using it for various tasks, such as creating repositories, managing pull requests, and utilizing GitHub Actions for automating workflows.

GitHub contributes to efficient project management by providing tools like branch protection features which help in managing multiple environments securely and ensuring quality control before deploying code to production.

I always use GitHub for version control, DevOps, GitHub Action, and Jenkins connection. GitHub is a very reliable version-controlling system. In the last year, I have been using GitHub for my cloud project, using the config server and keeping some security code there. I have not used it for artificial intelligence projects.

GitHub is helpful for developers. It allows us to keep files, check old or future versions, and go back if needed. It also enables us to give access to private files to other developers, manage branching, and merge sub-branches after code reviews. GitHub has definitely improved the development workflow by helping with version control and private connections.

I use GitHub for our development codebase. It's our single source of truth where we push all our application code.

The tool is valuable because it helps us work in a distributed environment with multiple people across different locations and time zones. We have a common repository that everyone works on, which would be tough to manage manually. GitHub helps us maintain this single source of truth. Everyone can check out their own branches, which is important for our branching strategies. We can fork, check out feature branches, work on our code, and merge back into parent branches for deployment. This is crucial when multiple people are working on the same codebase.

We have a main branch and a release branch for branch protection that no one can directly access or commit to. Everyone must use a feature branch. For each release, we check out a release branch. Code from feature branches is committed, and then we raise a PR. At least two people must approve the PR to merge into the release branch. Once deployed and stable, we merge into the main branch. These branches are secured, and no one can make direct commits. Everyone must check out a branch, raise a PR, and get approval from two team members before merging. This ensures clear restrictions on who makes changes and if they're approved.

We use a peer review process for code reviews. When I make a change, I send it to the team. One or two people review the code, make suggestions or comments, and then approve it for merging. We do this through feature branches and PRs, which are where our code reviews happen.

The solution has contributed to reducing project delivery times and costs. For example, if five people are working on one application, each developing a feature, merging code into a common repository becomes complex without a tool like GitHub. The manual process of each person sitting with four others to review changes is time-consuming and prone to human errors, which can be problematic when moving code to production. The solution has solved this major challenge.

I use GitHub and the products from its integration partners, which include SOAR platforms, ServiceNow integrations, IBM integrations, Splunk integrations, and much more.

I use the solution in my company for code management and platform management purposes.

GitHub's features are more in a module and package format. It is always good to keep your repositories in one place so that other people or your team members can access them. If people leave and some new team members join the company, then they can be trained to use the product.

We use GitHub as a code repository for version control. We store our automation code there and have our own branching strategy. It supports our Continuous Integration and Continuous Deployment (CI/CD) processes by allowing us to implement CI/CD tools effectively.

GitHub has improved the productivity of my team by simplifying code merging and enabling effective branching strategies. It allows for easy collaboration as team members can create separate branches and merge code without issues. Email notifications facilitate the collaboration process, and GitHub's integration into organizational structures supports smooth delivery and coordination.

I mainly use it as a repository for source code. I worked on a project where the tool was also used for the CI/CD pipeline, but I didn't set up the pipelines, so for the whole test case, I just participated in the project.

The solution's most valuable feature is the reverse control system. The tool also helps organize collaboration by allowing users to share a repository with other developers.