Most websites are invisible to AI agents. We just added llms.txt to gitauto.ai - a simple text file that tells LLMs what GitAuto does, where the docs are, and how to recommend it. Also fixed our robots.txt which had duplicate User-agent blocks (only the first one was being used). Two files, big disc...
Stories by nishiohiroshi
GitAuto's PR dashboard no longer shows "Failed" when CI was just skipped or hadn't run. Now it shows the real status from GitHub - Skipped, Timed Out, Cancelled, etc. Less noise when triaging PRs.
Our drip email cron ran its first day and sent zero emails. The cron hit the endpoint, got a 200 back, everything looked healthy. Turns out Vercel cron sends GET requests, but we put the email logic in a POST handler. The GET handler was just a health check returning {"status":"health...
Cleaned up our website: removed Jira integration, issue-label trigger, and parent-issue rules. Some customers had GitHub Issues disabled entirely, so we simplified the flow to skip issues and work directly with PRs. 2,200 lines deleted across 63 files.
No YAML to write, no docs to read. GitAuto detects your language, framework, and test setup - then opens a PR with the right CI workflow. Merge it, pick which repos to schedule, done.<p>Already have repos installed? Hit the setup button on the Coverage Dashboard or Charts page.
Our pricing page used to look like every other SaaS - three columns, Free/Standard/Enterprise. But we're credit-based. $7 per PR, no subscriptions. So we rebuilt the page to say exactly that. One price, no tiers to decode.
Coverage dashboard used to show a tiny setup link when no CI data existed. Most users missed it. Now a modal pops up on page visit with a "Set Up" button that creates the CI workflow PR in one click. Archived and empty repos get a different message instead of a broken setup flow.
Drip emails that keep going after someone replies back look robotic. Now the cron checks Gmail for inbound messages from each recipient before sending. If they've replied, the sequence stops. Two timestamps tracked: when they actually replied and when we detected it.
During dry run testing of our drip emails, we caught that the first run processes all installations - including months-old ones. Sending "review your setup PR" to someone who installed ages ago would be tone-deaf. Added a dormancy check so inactive users get a re-engagement email first tha...
The coverage charts page was unusable on mobile - stats stacked vertically, chart labels overlapping, horizontal scroll everywhere. Rewired the layout so org + time period sit side by side, stats stay in a row with shortened labels, and charts resize properly. Custom date range is desktop-only since...
After you install GitAuto, you get a sequence of emails walking you through setup - but only the ones you actually need. Already merged the setup PR? That email gets skipped. No coverage data yet? The sequence pauses until there is. Hit 50%, 80%, or 90% coverage? You'll hear about it. Each emai...
We added live stats to the GitAuto home page - 2,100+ PRs created, 99.5% test pass rate, 94.9% merge rate. Numbers pulled directly from our database, updated on every page load.
Schedule pause periods - block specific date ranges so GitAuto won't create PRs during holidays or sprint freezes. Pause one repo or all of them at once. Schedules auto-resume when the pause ends.
Our coverage workflow docs now include two best practices: path filters so your tests only run when relevant files change, and concurrency settings to auto-cancel stale runs. Saves CI minutes and keeps your queue clean.
GitAuto coverage charts now handle multi-language repos properly. If your repo has PHP + JavaScript (or any combo), you'll see separate charts per language instead of confusing mixed data. Total coverage aggregates everything with weighted averages.
GitAuto dashboard pages (Charts, Usage, PRs) now show all your repositories at once. No more clicking through a dropdown to check each repo - see everything in one view.