Extra suggestions:

• Add an option to only index the current/latest commit.
• Add a file filter. For example, my OneDev instance consumes all memory assigned to the container while indexing at least one specific file.

A code analysis setting already exists allowing include/exclude file patterns to be configured.

Ah, sorry, you're right.

@davidebeatrici I also experienced this issue recently. AI bots crawl each commit triggering indexing and this generates large index cache. I added a code index setting to optionally require logged-in user to trigger code indexing. It can be set in root projects and all child projects will inherit this setting.

I am closing this issue as it is no longer necessary with this option and code analysis pattern.

Great, thank you!

@robin I was wondering: can a system-wide setting be added to enforce the login requirement? Otherwise a project owner can change the setting at the expense of the server.

There is system wide setting (administration / project defaults) with an enterprise subscription. But project owner can still override that setting.