What would you like to be added:
Investigate whether bot account filtering in Git metadata generation is actively used, and either make it configurable or remove it entirely.
Why is this needed / describe a real-world scenario:
Docforge currently filters out CI bot accounts that are hardcoded in the source code during Git metadata generation. A team using Docforge with their own CI bots would need to modify source code to exclude their accounts from author/last-modified metadata. Before implementing a configurable solution, we need to confirm whether this feature is actively used anywhere.
Investigation steps:
- Locate hardcoded bot account list in the codebase
- Determine if the filtering logic is actively triggered in any deployment
- Check if the generated metadata is consumed anywhere (website, API, etc.)
Decision paths after investigation:
- Remove entirely if not actively used
- Make configurable if relevant for generic deployments
/kind technical-debt
/priority 3
What would you like to be added:
Investigate whether bot account filtering in Git metadata generation is actively used, and either make it configurable or remove it entirely.
Why is this needed / describe a real-world scenario:
Docforge currently filters out CI bot accounts that are hardcoded in the source code during Git metadata generation. A team using Docforge with their own CI bots would need to modify source code to exclude their accounts from author/last-modified metadata. Before implementing a configurable solution, we need to confirm whether this feature is actively used anywhere.
Investigation steps:
Decision paths after investigation:
/kind technical-debt
/priority 3