Help setting up honest-ci
Fixed-price projects in which honest-ci’s developer tunes it to your repositories, makes it part of your CI, and sets with you how pull requests from coding agents get reviewed.
Starter
One repository
$3,000 fixed price
Delivered in 28 days, 1 round of revisions
- Your last 100 merged pull requests replayed in your CI, and every flag gone through with your reviewer
- The rules and the policy tuned to your code, and up to 3 rules of your own
honest-ci/verifymade a required check, with who can let a held pull request through and how agent pull requests are handled- One tuning round after about two weeks of live pull requests
- Notes on every setting: what it does, why it’s set that way, how to change it
Standard
Up to 5 repositories
$8,000 fixed price
Delivered in 42 days, 2 rounds of revisions
- Everything in Starter, for each repository
- Up to 10 rules of your own
- A written policy for pull requests from coding agents, applied in every repository
- Two tuning rounds on live pull requests
- A guide for your reviewers on letting held pull requests through
Advanced
Up to 15 repositories
$15,000 fixed price
Delivered in 63 days, 3 rounds of revisions
- Everything in Standard
- The regression gate, on repositories whose test suite already runs with pytest or Maven
- Up to 5 judgment rules, if you turn on a model, on your own provider account
- Three tuning rounds on live pull requests
Prices are in US dollars and cover the setup work. A free license key covers the repositories in scope until 14 days after delivery; a subscription after that isn’t included, see Pricing. Delivery is counted in days from when the first milestone is funded and we have the details listed under What you provide. Projects are contracted and paid through Upwork, as Ordering describes.
How a project runs
- Agree the scope. We read your repositories, tests, agents and review process, and agree with you in writing which repositories are in scope and what counts as done.
- Replay your history. honest-ci runs in your CI over your recent merged pull requests, and we go through every flag with your reviewer.
- Tune and switch on. The tuned rules, policy and workflow are merged, the check becomes a merge requirement, and approvals and agent pull requests are set up.
- Tune on live pull requests. After about two weeks, we go through what it held and what it let through, and adjust.
- Hand over. Notes on every setting, and how to change it when your code or your agents change.
What you provide
- Your GitHub organization or account, and the repositories in scope, with their languages and test frameworks. They need to be on GitHub and use GitHub Actions.
- Which coding agents open pull requests in them, and under which accounts or apps.
- Your GitHub plan, and who on your side can change repository settings, branch protection and secrets.
- Someone on your team to go through the flags with us, and their GitHub username.
- Write access to the repositories in scope, as an outside collaborator. Every change comes as a pull request for you to review and merge, and we don’t approve your pull requests. Your admin changes settings such as branch protection and secrets, following written steps from us.
Your code
- honest-ci runs on your GitHub Actions runners, so your code runs only in your CI, the replay included.
- We read the code, pull requests, commit history and CI logs of the repositories in scope ourselves. They go into no AI tool, translation service or other outside service: apart from your GitHub, and the Upwork messages and email we use with you, nothing else processes them.
- Your code isn’t used in honest-ci, in articles or in any public material without your written consent. Our copies of it are deleted when the 14 days of fixes after delivery end.
- We never hold your secrets or tokens. honest-ci’s model, if you turn it on, runs under your own account with its provider.
What isn’t included
- An honest-ci subscription after the project. During it, a free license key covers the repositories in scope, until 14 days after delivery. After that, a team’s private and internal repositories need a paid license: see Pricing. Public repositories, and private ones under a personal account while only its owner opens pull requests on them, never need one.
- Platforms other than GitHub, and CI systems other than GitHub Actions.
- Making a test suite runnable, or fixing your code or your tests.
- New honest-ci features, and work unrelated to honest-ci.
- Access to production systems or to personal data.
Ordering
- Email us at support@honest-ci.dev with the package you want and the repositories it is for. We reply with any questions and the date work can start.
- We send a fixed-price contract through Upwork, with the package’s scope and price, in two milestones of 50% each. The first covers the replay, the tuning and switching the check on (on your first repository, for Standard and Advanced); the second covers the rest of the rollout, the tuning rounds and the handover. If your company isn’t on Upwork, it is an Upwork Direct Contract, sent to your email. If it is, we tell you how to hire us there.
- Each milestone is paid into Upwork’s escrow before work on it starts, and released to us when you accept it.
Questions
- What counts as done?
- We agree acceptance criteria in writing before work starts. By default: on the replayed pull requests, your reviewer agrees that at least 9 in 10 of the flags left after tuning were worth a look. A rule that can’t get there on your code is set to record only, with the reason written down.
- What happens after delivery?
- Bugs in what we set up are fixed free of charge for 14 days after delivery. After that, changes are a new project.
- Who owns what?
- The configuration files and notes written for you are yours. honest-ci stays under its own license, the Fair Core License (FCL-1.0-ALv2).
- Where are you, and how do we talk?
- In mainland China (UTC+8). We prefer written communication, on the pull requests and by email; calls are available.