# Zero lint errors required before docs merge

> Block the merge when a docs branch still has lint errors so the live hub stops inheriting known quality debt by policy.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/zero-lint-errors-required-before-docs-merge/
- Source: [docs.readme.com](https://docs.readme.com/main/docs/reviews)
- GrowthDex source hub: [ReadMe Docs: Reviews](/sources/readme-docs-reviews-docs-readme-com/)
- Last checked: 2026-06-06T09:04:00Z
- Rarity: rare
- Budget: low
- Channels: Documentation, SEO, Operations
- Stages: documentation, merge gate, quality control, technical seo


## Why this can grow

Teams often say quality matters, then let known docs issues ship because the merge button is easier than the cleanup. ReadMe's review settings make a firmer rule available: do not merge if lint errors still exist on the branch. That matters because documentation debt compounds through every support reply, onboarding flow, and search result that points at the page. A blocked merge is cheaper than a public correction once the bad route is already circulating.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where zero lint errors required before docs merge can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Documentation and SEO channel.
3. Use the evidence from docs.readme.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

ReadMe's Reviews settings include Zero Lint Errors, which prevents users from merging changes if there are lint errors on the branch.

## Adjacent tactics in the same lane

- [Teammate approval before docs merge on critical docs](/growth-ideas/teammate-approval-before-docs-merge-on-critical-docs/) - same source, 1 shared channel, 1 shared stage
- [Docs linter runs before save, not after publish](/growth-ideas/docs-linter-runs-before-save-not-after-publish/) - 3 shared channels, 2 shared stages
- [Preview docs noindex before cutover](/growth-ideas/preview-docs-noindex-before-cutover/) - 3 shared channels, 1 shared stage
- [Regex redirect families before docs group migration](/growth-ideas/regex-redirect-families-before-docs-group-migration/) - 3 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The docs route should fail in review, not in public](/blog/the-docs-route-should-fail-in-review-not-in-public/) - documentation, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.