Troubleshooting

Check that it was included when you installed the GitHub App. To adjust which repos it can see, use “Manage repos on GitHub” next to the account on the Repos tab; changes there sync back automatically. Also check you have not hit the repo limit on the Plan page (see Billing & plans).

That account or organisation already had Amendary installed, so GitHub showed its settings page instead of returning to Amendary. “Connect GitHub” now lists the accounts and organisations where Amendary is installed and lets you pick one, so select it again from the Repos tab and choose the account there.

Amendary can only see pages you shared with the integration when you connected Notion, and Notion search is not exhaustive. If a page is missing from “Browse workspace”, reconnect Notion and select it (or its parent) in Notion’s picker, or paste its link into “Add by Notion URL” on the Pages tab. Note that pages inside a database appear when you expand that database in Browse.

The page was deleted or unshared in Notion, so Amendary can no longer read it and stops checking it. It is hidden from your watched list; you can show gone pages to review them. If it still exists, reconnect Notion and select it again; if it is really gone, you can remove it.

Help-center pages follow the repo’s change trigger, and that trigger has no signal yet. The usual case: GitHub Releases is chosen but the repo has never published one, so there is nothing to check against. Open the Repos tab and look for the “No signal for this trigger yet” warning. Then either publish a release or push a tag, set the branch name, or switch the trigger to commits, which needs no setup.

Disconnecting only stops Amendary from syncing; it does not delete anything on GitHub or Notion. Reconnect from the Repos, Pages, or Settings tab to pick up where you left off.