Ellie Help
Ellie Help Home What's new Getting started9 Work with Ellie4 Write and organise content7 Keep your docs up to date1 Publish and brand3 Walkthrough videos2 Changelog2 Measure and improve1 API reference1 Workspace and billing6 Connect AI tools1
Security and data3
Troubleshooting1
Powered by Ellie Docs
Security and data/Exclude files from scanning

Exclude files from scanning

Updated 19 Nov 2026

On this page

You can keep specific folders or file patterns out of repository analysis for a project. This helps you focus Ellie on the parts of your codebase that should shape your docs.

Step by step

  1. Open your project, then go to Settings → Repositories.
    The Repositories tab showing connected repositories and their current analysis summary
  2. Find the repository you want to change, then click Skip folders or Edit on its exclusion line.
    The repository list with the Skip folders action on a repo exclusion line
  3. In the exclusions dialog, choose the folders you want to skip. If the dialog is showing patterns instead of a folder tree, enter the patterns you want to exclude there.
  4. Click Save.
  5. Review the impact dialog, then confirm the change.

Common ways to use exclusions

Teams typically exclude parts of a repository that should not drive help-centre content, such as generated output, vendor code, or folders unrelated to the product surface you document.

If you want Ellie to focus on only part of a repository, the exclusion settings can also switch the repo to analysing only selected folders instead of the whole repo.

What changes after you save exclusions

Saving exclusions changes which files are analysed for that repository. The repository summary updates to show what Ellie is analysing, such as the whole repo, only selected folders, or skipped folders, along with the number of files being analysed.

Your saved change can also trigger reanalysis for that repository, and content affected by the excluded source can be updated to reflect the new scope.

Use exclusions when a connected repository contains large areas that should never influence customer docs, such as build output, third-party code, or unrelated apps in a monorepo.

Good to know

  • Exclusions are set per repository, not once for the whole project.
  • The same exclusions dialog is also available during onboarding when you connect repositories.

See also: What code Ellie reads and what it never reads and Project settings reference

Recent updates

All updates →
On this page