Software Alternatives, Accelerators & Startups

Commit Together by Github VS RunsOn

Compare Commit Together by Github VS RunsOn and see what are their differences

Commit Together by Github logo Commit Together by Github

Now add co-authors to your commits

RunsOn logo RunsOn

Access the fastest and cheapest self-hosted runners on the market with a one-line change. Easily installable in your own AWS account. x64 and arm64 architectures supported.
  • Commit Together by Github Landing page
    Landing page //
    2022-11-04
  • RunsOn 10x cheaper GitHub Action runners
    10x cheaper GitHub Action runners //
    2024-01-23
  • RunsOn Cheaper AND faster than BuildJet / Warpbuild / GitHub
    Cheaper AND faster than BuildJet / Warpbuild / GitHub //
    2024-01-23

Cheap runners are just one part of the equation: nobody likes slow runs, even if it's cheap.

RunsOn gives you access to some of the fastest machines on the market, thanks to AWS extensive hardware selection.

Which makes RunsOn the fastest provider of self-hosted, fully ephemeral runners on the market.

We automatically build and publish copies of the official runner images at most 24h after their official release, so that you can be certain that your workflows will always work on either GitHub runners, or your own RunsOn runners.

Commit Together by Github

Pricing URL
-
$ Details
-
Platforms
-
Release Date
-

RunsOn

$ Details
freemium €300.0 / Annually
Platforms
AWS GitHub
Release Date
2024 January

Commit Together by Github features and specs

  • Enhanced Collaboration
    Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
  • Improved Code Review Process
    With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
  • Accountability
    By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
  • Efficiency in Pair Programming
    When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages of Commit Together by Github

  • Complex Commit History
    Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
  • Potential Workflow Conflicts
    Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
  • Initial Setup Overhead
    Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
  • Tooling Compatibility
    Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

RunsOn features and specs

  • Ephemeral self-hosted runners
  • Autoscaling
  • Pricing
    10x cheaper than competition

Category Popularity

0-100% (relative to Commit Together by Github and RunsOn)
Productivity
100 100%
0% 0
Developer Tools
54 54%
46% 46
GitHub
0 0%
100% 100
User Experience
100 100%
0% 0

Questions and Answers

As answered by people managing Commit Together by Github and RunsOn.

What makes your product unique?

RunsOn's answer:

10x cheaper than GitHub official runners. Runs in your own AWS account. More secure than sharing your secrets with other third-party tools like BuildJet or Warpbuild.

Why should a person choose your product over its competitors?

RunsOn's answer:

Cheap, fast, on-premise alternative to maintaining self-hosted runners.

How would you describe your primary audience?

RunsOn's answer:

CTO / Senior developers

What's the story behind your product?

RunsOn's answer:

Built a similar product for one of my clients, reduced CI build cost by 10 times, and improve build speed from 1h to 20min.

User comments

Share your experience with using Commit Together by Github and RunsOn. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, RunsOn should be more popular than Commit Together by Github. It has been mentiond 6 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Commit Together by Github mentions (1)

  • Ask HN: Do you rewrite pull requests?
    There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / about 3 years ago

RunsOn mentions (6)

  • Managed, self-hosted Arm runners for GitHub Actions using AWS Graviton Processors
    RunsOn is a self-hosted runner manager for GitHub Actions that you can install in your own AWS account. It will automatically spawn EC2 VMs as self-hosted runners for your GitHub Actions workflows. - Source: dev.to / 8 months ago
  • Ask HN: What are you working on (August 2024)?
    I'm working on https://runs-on.com, a self-hosted solution to get 10x cheaper GitHub Actions runners with support for Linux x64 and arm64. This month I've been refining Windows support and hopefully this gets fully shipped before Aug 31st! - Source: Hacker News / 9 months ago
  • Ask HN: Any CI/CD SaaS Solutions for ARM?
    You could also be interested in https://runs-on.com. Must be installed in your AWS account (1-click cloudformation template), and then you can use any instance type offered by AWS. - Source: Hacker News / 10 months ago
  • GitHub now provides Arm-based runners
    > We were using self-hosted runners which were not as efficient as we thought so we spawned EC2 instances and connected them to the github network to be runners, but we had such an amount of issues that we wanted to go back to non-self hosted For those hitting that same kind of issue (and you are many), you should check out my product https://runs-on.com. 1-click install, 1-click upgrades, and from 7x to 16x... - Source: Hacker News / 11 months ago
  • Making EC2 boot time 8x faster
    > while we can boot the Actions runner within 5 seconds of a job starting, it can take GitHub 10+ seconds to actually deliver that job to the runner This. I went the same route with regards to boot time optimisations for [1] (cleaning up the AMI, cloud-init, etc.), and can boot a VM from cold in 15s (I can't rely on prewarming pools of machines -- even stopped -- since RunsOn doesn't share machines with multiple... - Source: Hacker News / 12 months ago
View more

What are some alternatives?

When comparing Commit Together by Github and RunsOn, you can also consider the following products

Commit Print - Posters of your git history

BuildJet for GitHub Actions - We provide users with managed high-performance runners for Github Actions.

CommitTasks - A small CLI tool that combines git commit and todo list 🛠📝

Cirun.io - GitHub Actions on your Cloud!

Refined GitHub - Browser extension that makes GitHub cleaner & more powerful

VS Code - Build and debug modern web and cloud applications, by Microsoft