Choose branches, triggers and path filters

Configure each Autopilot repository link to match the code that should influence a Space.

Branch

Use the branch whose behavior the documentation describes. A Space documenting released behavior may need a different branch from an experimental internal Space. Check exact spelling and revisit the link if the repository changes its branch naming.

Triggers

Choose the supported events for that provider, such as pushes or merged pull requests. Providers send different event shapes, so pull-request behavior can vary. Review actual activity after configuration to verify the expected event is recognized.

Path filters

Use filters when only part of a repository belongs to the documentation. For example, a backend API Space may focus on api/ or app/ rather than a separate website directory.

Enter filters in the format accepted by the settings control. If an event touches no matching files, it does not produce suggestions for that link. Overly narrow filters can exclude a dependency whose change matters to your docs.

Instructions

Provide factual writing guidance relevant to the Space, such as the audience or terminology. Instructions help shape suggestions but do not make unrelated changes relevant or guarantee an update for every event.

After changing scope, inspect a representative event in Activity and review the resulting suggestions. If expected updates are absent, compare the actual changed paths with the saved filters before changing the documentation itself.