Problem:
Many AI tools (Copilot, Gemini, Roo, etc.) support their own ignore files (e.g., .copilotignore, .geminiignore) to exclude files from their context. When using multiple tools in a project, developers have to maintain several ignore files with largely identical content. This is redundant and error-prone.
Proposal:
Introduce a feature to generate these tool-specific ignore files from a single, central file named .rulesyncignore.
-
Create a .rulesyncignore file: Users will create a .rulesyncignore file in the project root, using the same syntax as .gitignore.
-
Extend the generate command: The rulesync generate command will be updated to:
- Read the content of
.rulesyncignore.
- Write that content to the respective ignore files for each supported tool (e.g.,
.copilotignore, .geminiignore, .rooignore).
Benefits:
- Single Source of Truth: Manages all ignore rules in one place.
- Consistency: Ensures consistent behavior across all AI tools.
- Simplified Maintenance: Reduces the effort of keeping multiple configuration files in sync.
This will allow developers to manage ignored files efficiently, following the DRY (Don't Repeat Yourself) principle. The rulesync gitignore command should also be updated to add the generated tool-specific ignore files to the project's .gitignore.
Problem:
Many AI tools (Copilot, Gemini, Roo, etc.) support their own ignore files (e.g.,
.copilotignore,.geminiignore) to exclude files from their context. When using multiple tools in a project, developers have to maintain several ignore files with largely identical content. This is redundant and error-prone.Proposal:
Introduce a feature to generate these tool-specific ignore files from a single, central file named
.rulesyncignore.Create a
.rulesyncignorefile: Users will create a.rulesyncignorefile in the project root, using the same syntax as.gitignore.Extend the
generatecommand: Therulesync generatecommand will be updated to:.rulesyncignore..copilotignore,.geminiignore,.rooignore).Benefits:
This will allow developers to manage ignored files efficiently, following the DRY (Don't Repeat Yourself) principle. The
rulesync gitignorecommand should also be updated to add the generated tool-specific ignore files to the project's.gitignore.