🛡️ AI Findings > Ackowledge the findings about `_site/docusaurus.config.js`

[adriens]

❓ About

We activated AI findings We need to acknowledge the _site/docusaurus.config.js finding :

🎯 Actions

• Make an issue to Gh support to know how to exclude:acknowledge it
• Get back to a situation where we have 0 AI findings

[adriens]

Github support contacted : https://support.github.com/ticket/personal/0/4075834

[adriens]

Waiting for GH support.
⏸️

[adriens]

[adriens]

New ping to GH support (still not a single response nor arcknowledgment) :

[adriens]

@Supervinh , we got the answer, see below steps :

GitHub Support
Hi Adrien,

For AI findings, there is not currently an “acknowledge/ignore this alert forever” flow like you see with Dependabot alerts or CodeQL code scanning alerts. AI findings are focused on suggestions for recently changed files, and the main control available today is to dismiss individual findings.

To handle findings that come from generated Docusaurus output, these are the best options:

1. Dismiss the finding in AI findings
   Go to https://github.com/opt-nc/geol/security/quality/ai-findings
   Open the finding for the generated file such as site/docusaurus.config.js
   Use the Dismiss option for that finding, and add a short reason like “Generated by Docusaurus”
   If the same suggestion reappears after the file changes again, it will need to be dismissed again

2. Keep generated output out of the default branch history if possible
   If site/ is build output, the most reliable way to prevent recurring AI findings is to avoid committing generated artifacts to the default branch. Common approaches are:
   Commit only the source inputs for Docusaurus, and build site/ in CI
   Publish the built site to GitHub Pages from a workflow or a separate publishing branch, instead of storing generated files in main

3. If you must keep the generated files in the repo, isolate them
   If generated files must be committed, try to keep them in a dedicated directory and limit changes to them. AI findings key off recently changed files, so the fewer changes land in site/, the fewer AI findings you will see there.

To confirm this is resolved on your side, please try dismissing the specific finding and then check that it moves to the Dismissed tab and no longer shows as Open for the current state of main.

If you can share one example URL of a specific finding details page you want to “acknowledge” permanently, and confirm whether site/ is generated output or source code you maintain, I can suggest the cleanest repo structure for your case.

Regards,

Abby
Enterprise Support Engineer
GitHub.com

[adriens]