Implemented in ci-toolkit
GitHub pull request title checks ↗
Validate GitHub pull request titles with Conventional Commits. See ci-toolkit configuration, squash-merge behavior and enforcement limits.
The workflow library / early access
Small automations.
Useful consequences.
Practical guides to the checks and handoffs around a build. Start with what already runs in ci-toolkit, then explore where Runnerless could take it.
12 implemented capabilities
What ci-toolkit
already does.
These features exist in our private GitHub App. They are the working foundation for Runnerless, whose public runtime and integrations are still in development.
Implemented in ci-toolkit
Conventional Commit checks for GitHub ↗
Check individual GitHub PR commit messages against Conventional Commits with ci-toolkit, including pagination limits and default-branch policy.
Implemented in ci-toolkit
A Codex review gate for GitHub pull requests ↗
Require a trusted Codex verdict for the current PR head, resolved threads and fresh review evidence before a GitHub pull request can merge.
Implemented in ci-toolkit
Automatic Codex reviews on new PR commits ↗
Request a Codex review for each new GitHub PR head with ci-toolkit’s auto-review label, without duplicating requests for the same head.
Implemented in ci-toolkit
Merge GitHub pull requests with /merge ↗
Use an authorized /merge comment for squash or merge commits, with GitHub checks, base freshness and repository merge-method rules enforced.
Implemented in ci-toolkit
Validate CI automation configuration in a PR ↗
Catch invalid .ci-toolkit.yml before merge with a read-only GitHub check for policies, artifact automations and release version files.
Implemented in ci-toolkit
Publish BuildBuddy test reports on GitHub PRs ↗
Publish verified BuildBuddy HTML artifacts to public storage and upsert a GitHub PR comment with the report link, checksum and expiry.
Implemented in ci-toolkit
Publish CI artifact folders and binary bundles ↗
Stream BuildBuddy artifact sets to public storage with file patterns, per-file checksums, PR links and bounded default-branch retention.
Implemented in ci-toolkit
Stable CI artifact URLs for a commit ↗
Resolve published CI files by repository and Git commit SHA, with a folder index, JSON listing, expiry handling and verified storage targets.
Implemented in ci-toolkit
Automated GitHub releases from Conventional Commits ↗
Use ci-toolkit to prepare a release PR, update a version file and changelog, then create a Git tag and GitHub Release after merge.
Implemented in ci-toolkit
GitHub rulesets for trusted CI checks ↗
Pin App-owned review and policy checks to a GitHub ruleset, require a fresh base and keep enforcement synchronized with trusted configuration.
Implemented in ci-toolkit
Reliable GitHub webhook automations ↗
See how ci-toolkit handles repeated webhooks, queued artifact work, reconciliation, health checks and bounded retries in a Cloudflare Worker.
6 directions to explore
Where this
could go next.
Design concepts with proposed workflows and explicit limits. These are not released features or launch commitments.
Runnerless concept · not available yet
Repository policy checks without a CI runner ↗
A Runnerless concept for fast license, file-layout and repository sanity checks, building on ci-toolkit’s existing PR policy enforcement.
Runnerless concept · not available yet
Shared JavaScript checks across CI workflows ↗
A proposed Runnerless approach to reuse JavaScript policy logic from YAML or code configuration while keeping existing CI builds in place.
Runnerless concept · not available yet
Artifact publishing across CI providers ↗
A planned Runnerless workflow for consistent artifact links and PR comments across GitHub Actions, CircleCI, GitLab CI and BuildBuddy.
Runnerless concept · not available yet
Deploy compiled Cloudflare Workers from CI artifacts ↗
A Runnerless concept for publishing verified compiled Cloudflare Worker artifacts, with explicit optimization, deployment and rollback decisions.
Runnerless concept · not available yet
Deployment approvals tied to an exact artifact ↗
A proposed Runnerless workflow connecting release approval, commit-addressed artifacts and explicit deployment actions across hosting platforms.
Runnerless concept · not available yet
Custom AI hooks for repository workflows ↗
A planned Runnerless approach to AI hooks for issues, comments, reviews and proposed changes, with explicit tool permissions and workflow actions.
Help choose what comes next
Which workflow
would you use?
Get early access ↗Register unverified early interest. No product account or installation is created.