gemini-cli - 💡(How to fix) Fix agents/ directory convention conflicts with GitHub Enterprise push protection [1 participants]

TL;DR

Allowing the sub-agents directory to be configurable in gemini-extension.json is likely the most effective fix for the conflict with GitHub Enterprise push protection rules.

Guidance

• Consider changing the default sub-agents directory to a non-reserved path, such as subagents/ or gemini-agents/, to avoid conflicts with GitHub's AI agent features.
• If changing the default is not feasible, adding a configurable agentsDirectory option in gemini-extension.json would provide extension developers with a workaround.
• Verify the fix by attempting to push an extension with a sub-agent to a GitHub Enterprise org with the restricted path ruleset enabled.
• Test the push with both the default and custom sub-agents directory configurations to ensure the fix works as expected.

Example

A potential configuration for gemini-extension.json could be:

{
  "agentsDirectory": "subagents/"
}

This would allow extension developers to use a custom sub-agents directory that does not conflict with GitHub's reserved paths.

Notes

The effectiveness of this fix may depend on the specific GitHub Enterprise org configuration and the level of access granted to non-admin users.

Recommendation

Apply a workaround by allowing the sub-agents directory to be configurable in gemini-extension.json, as this provides a flexible solution for extension developers to avoid conflicts with GitHub's reserved paths.