diff --git a/fern/docs/core-concepts/triggers.md b/fern/docs/core-concepts/triggers.md index 62ed46d..f993fc0 100644 --- a/fern/docs/core-concepts/triggers.md +++ b/fern/docs/core-concepts/triggers.md @@ -22,6 +22,12 @@ During analysis, Promptless processes information such as the code diff, PR titl You can configure specific directories to monitor, focusing documentation efforts on relevant parts of your codebase. +#### What Gets Analyzed + +When a PR triggers Promptless, we only analyze the files that changed in that PR. We don't search your entire repository—just the specific files shown in the diff. + +This focused approach means Promptless understands exactly what's changing and generates accurate documentation updates based on those specific changes. + When auto-publish is enabled for your project: diff --git a/fern/docs/faq.mdx b/fern/docs/faq.mdx index efff6aa..804f311 100644 --- a/fern/docs/faq.mdx +++ b/fern/docs/faq.mdx @@ -26,6 +26,10 @@ However, you can optionally enable **passive listening** for specific channels. For more details, see our [Slack Integration documentation](/docs/integrations/slack-integration) and [Working with Slack](/docs/features/slack-interactions#4-passive-channel-listening). +### Does Promptless analyze my entire codebase? + +No. When triggered by a pull request, Promptless only analyzes the changed files in the PR diff—it doesn't search across your entire repository. This focused approach helps Promptless understand exactly what changed and generate relevant documentation updates. + ### How does Promptless handle my data? Promptless follows strict data handling practices: