AWS CodeCommit vs GitHub: What are the differences?
Developers describe AWS CodeCommit as "Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git repositories". 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. On the other hand, GitHub is detailed as "Powerful collaboration, review, and code management for open source and private development projects". 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.
AWS CodeCommit and GitHub can be primarily classified as "Code Collaboration & Version Control" tools.
Some of the features offered by AWS CodeCommit are:
- Access Control
On the other hand, GitHub provides the following key features:
- Command Instructions
- Source Browser
- Git Powered Wikis
"Free private repos" is the primary reason why developers consider AWS CodeCommit over the competitors, whereas "Open source friendly" was stated as the key factor in picking GitHub.
reddit, Instacart, and Lyft are some of the popular companies that use GitHub, whereas AWS CodeCommit is used by iMedicare, Complete Business Online, and Sidecar Interactive. GitHub has a broader approval, being mentioned in 4647 company stacks & 5874 developers stacks; compared to AWS CodeCommit, which is listed in 24 company stacks and 17 developer stacks.
What is AWS CodeCommit?
What is GitHub?
Want advice about which of these to choose?Ask the StackShare community!
I use GitHub because since it was bought by Microsoft, some new features are being introduced in and most importantly, the git clone speed is usually much faster than gitlab. Gitlab is very good, I like the member permission function which is good for collaborative coding. But still I am more used to github interface.
I prefer to use GitHub because their website speed is faster and the availability more reliable than the competitors, this is our top priority as GitHub is our core functionality we need to be able to operate in development. And since their new pricing make more sense and work for us as they are charging based on how many developers than repositories, this help us to keep our repositories smaller by dividing each codebase into specifics repositories.
The world we currently live in consists of Jargon technologies and with each passing day a new technology is introduced in the market which serves to improves the life in one or the other way. #Github is one of the splendid Version Control repository management services which has a key component in the software development workflow and has a greater impact on developers life giving valuable essence to utilize the best tools fitted for any product.
In the last few years, GitHub and GitLab positioned themselves as handy assistants for developers, particularly when working in large teams. I use GitHub because it has overcome my time in maintaining code and product #Repositories. #GitHubPullRequests along side with #GithubIssues have helped me and many moderators like me to keep a track of the #commits done by any number of people around the world.
People synchronization to various roots of our project repositories has made our product to stand Safe Secure Accessible and #Feasible The newer addition to #GithubMarket and #ToolsForGithub has helped our community to use various in-built applications which provided us to track up with #Documentation, #Licensing #Codebase-Hosting and #DependencyMonitoring
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.
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.
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.
Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff, like Travis CI. But the command bar has disappeared...
It's the best tools I have ever used.
"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)."
Pervasive, easy to use Git repo hosting. I host ongoing personal projects privately and my personal blog (via GitHub Pages).
I also take successful proofs of concept (for example, experimenting with linking AWS Lambda to Heroku Postgres to create a serverless SQL backed web app), and host them as public example repos. These are linked to Dependabot and CircleCI if they have tests so that dependencies can be kept up to date automatically over time and the code using the dependencies can stay fresh over time for example viewers.
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
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).