Amendary only checks pages you've explicitly watched and mapped to a repo. This page covers how to add pages, tell Amendary what kind of content they are, and control when they get checked.

Choosing where your docs live

Before you map anything, go to Pages and select Where do your docs live?. You can watch a Notion page or a GitHub docs folder (either a repository's docs/ folder or its wiki), and a workspace can connect more than one GitHub account and more than one Notion workspace, so pages from different sources all show up in the same list. GitHub docs always map to the repo they live in.

To watch a Notion page, paste its page link or ID. To watch a GitHub destination, choose the repo and the folder, and decide whether corrections should be opened as a pull request or committed directly, and whether only the connection owner can write to it (Owner only).

<aside> ✏ If a repo has no GitHub destination configured yet, add one from Add destination before you can watch its folder.

</aside>

Setting a page's audience

Every watched page needs an audience, which tells Amendary how to judge whether it has gone stale:

Select one or more pages in the list, then use Set audience for selected pages to apply it in bulk, or set it per page. A page that has never had an audience set shows as not watched yet; only pages in that state can take the audience you choose for new mappings.

Setting a document type

Alongside audience, choose the page's document type, which controls the shape of corrections Amendary writes:

Document type What it does
Docs & guides Sentences are corrected as the code changes
On-call runbook Keeps prerequisites, steps and verification current
Incident playbook Covers diagnosing a failure, limiting impact and verifying recovery
Product updates Adds dated entries as the repo ships
Architecture decisions One record per decision, sourced from pull requests and commits

Not every type is available for every audience: engineering docs can use runbooks, incident playbooks and architecture decisions in addition to docs and guides; help center pages can use docs and guides or product updates. Product updates is also unavailable if the page's destination is GitHub, since the changelog publishes to Notion only. Use Set type for selected pages to apply a type to more than one page at once.

Setting the change trigger

For a repo's help-center pages, set the Change trigger on the Repos screen: commit (the default), branch, release, or tag. Engineering docs always react to commits regardless of this setting. If a repo's chosen trigger has no usable signal yet (for example, a release trigger on a repo with no releases), the page shows that the trigger isn't ready, so you know why nothing has been checked.

You can also set Also trigger on changes from a second repo when a help-center page depends on more than one codebase, and skip pull requests carrying specific labels so draft or internal work doesn't trigger a check.

Pausing checks on a page

To stop checking and editing a page without unmapping it, select it and choose Pause checks. This sets its audience to Checks paused: Amendary keeps the page's repo mappings but stops reading it until you set a real audience again.