Sign in to Ferndesk as an owner or admin, in the workspace where you started connecting. If you switched workspaces in another tab, switch back and connect again.
Connect GitHub
Connect GitHub so Fern can read your code and merged pull requests. Fern uses them to write accurate articles, to draft updates when you ship, and to refresh API references when the code changes. Fern only reads your code.
Owners and admins can connect GitHub and choose which repositories Fern uses.
Install the Ferndesk app
Start from Integrations, then install the Ferndesk app on GitHub and pick the repositories it can see. One installation can cover a product split across several repositories, such as a backend and a dashboard.
If you cannot install apps in your GitHub organization, GitHub sends an install request to its owners. Once they approve it, choose Connect again to finish. If you only sign in without installing the app, Fern cannot draft from merged pull requests.
Running several Ferndesk workspaces on one GitHub installation? Choose Reuse a GitHub connection instead of authorizing again. You need to be an owner or admin in the workspace the connection comes from. Its repositories start switched off in the new workspace.
Choose the repositories Fern uses
Each repository the installation shares has a switch for whether Fern uses it for docs. New repositories start switched on.
Switching a repository off keeps it out of Fern's code research and pull request drafts in this workspace. The GitHub app can still see it.
To share more or fewer repositories, choose Change repositories on GitHub from the connection's menu.
With Support, Fern reads every shared repository when it looks into a customer's conversation, whatever the switch says.
Set the production branch
The production branch is the one your customers run. A pull request counts as shipped when it merges into it, and that is what drafts from merged pull requests react to. Each repository uses its default branch until you pick another in the Production branch column. If that branch is no longer on GitHub, the repository moves to the top of the list with a note. If the branch was deleted, Fern goes back to the default branch. If it was renamed, pick the new name in Production branch.
Troubleshooting
Connecting fails with a sign-in or workspace error
Connecting fails with an access error after I authorize
The GitHub account you used cannot see the Ferndesk app installation. Ask an owner or admin of that GitHub organization to connect.
Fern does not draft from merged pull requests
Check that the repository is switched on, that its production branch is the one you merge into, and that Draft from merged PRs is not off in Fern > Customize > Automations. Drafts need the GitHub app installed. A GitHub sign-in alone is not enough.