Favorites

Fans

116

Votes

153

Jobs

0

Favorites

Fans

24

Votes

8

Jobs

110

Hacker News, Reddit, Stack Overflow Stats

Description

What is
GitHub?

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

What is
AWS CodeCommit?

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

What is
Perforce?

Visibility, access control, workflow and code management for Git environments. Flexibility of collaborating on the same codebase and code reviews using any combination of Perforce and Git workflows and tools without compromise.

Want advice about which of these to choose?Ask the StackShare community!

Reviews of GitHub, AWS CodeCommit, and Perforce

I love GitHub! They provide a completely free service for hosting, storing, and collaborating on code. Seriously, if you aren't using them, go sign up now.

Ease of Use
Documentation
Reliability
Support

sivakumar-kailasam

Why GitHub is more friendlier than other services I've used.

March 23, 2014 23:10

For starters you can fork a repo, edit it online and send a pull request which is huge if its something very small that you want to commit. The whole pull request system, the UI and the UX are great. If I sent out a pull request that failed on travis CI then all I need to do is fix it in my fork and the original pull request will have these updates as well making it super easy for everyone involved. Overall a great service.

Ease of Use
Documentation
Reliability
Support

tbodt

Very nice

November 06, 2014 13:19

Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff, like Travis CI. But the command bar has disappeared...

Ease of Use
Documentation
Reliability
Support

princesust

Awesome

July 07, 2015 23:15

It's the best tools I have ever used.

Ease of Use
Documentation
Reliability
Support

AnakinPt

Very hard to handle

July 31, 2018 02:34

The pull requests are only merged by FF what makes all the merges hard to manage. The IAM configuration is very awkward and the unavailability to add git hooks to prevent commits to be made into the server makes this tool not much usable for a software development company.

Ease of Use
Documentation
Reliability
Support

How developers use GitHub vs AWS CodeCommit vs Perforce

"Having a CI server building all commits across all branches was a huge first step, but to make this useful we needed to surface the outcome of these builds. This is where GitHub’s commit status API comes in. Every time our CI server begins a build, it pings GitHub’s commit status endpoint, and every time it completes a build it hits the endpoint again with the outcome. Now every open PR includes a yellow/red/green indicator for the branch in question, with a direct link to the build status page on our CI server. In practice this means more transparency, faster feedback cycles, and a guarantee that every branch merged into master has a passing test suite. This integration has been a huge help in keeping our master branch green, and has thus greatly reduced our deploy times (since engineers aren’t waiting on build failures to be resolved in master)."

Yeah, so we use GitHub, and we basically use a variant of continuous deployment where when anyone merges in a feature that they’ve finished with, they ship it immediately, and we bundle it up as a build pack and send it to all of our EC2 servers... Any developer on the team can trigger a build and deploy at any time. So on a given day, we probably deploy 20 or 30 times to prod.

One thing I really wish GitHub had: Trello-style kanban for Issues. There are a bunch of services and tools that add Kanban to GitHub Issues. But Trello just seems far better. If GitHub had it’s own kanban tool, I’d probably use it. Right now it’s pretty painful to try to tie cards to commits manually (when/if we remember to).

healthchecks.io is an open source project, and its source is available on GitHub. We use GitHub issues to track bugs and feature requests. We have received some substantial pull requests and are happy for that.

GitHub was where both technical and non-technical people collaborated on the source code, and was used with Buildkite and Heroku’s integrations for testing and deployment. Non-tecnical people on the project used GitHub’s web UI to update markdown files, replace images, and help edit typos and copy.

been using github for a bit. used the pull-request and issues system to manage code. love the code review features. use gists to save snippets of useful code. have various repos of code written in the last decade.

Self taught : acquired knowledge or skill on one's own initiative.
repository to share and learn. where people build software and write articles about projects : contains the complete history of the project from its inception.

GitHub is a Web-based Git version control repository hosting service. It is mostly used for computer code. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project

GitHub is a web-based hosting service for version control using Git. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.