gemini-cli - 💡(How to fix) Fix Support per-project local settings [2 comments, 2 participants]

TL;DR

Implement a configuration merge mechanism to prioritize settings from a local-only file, such as .gemini/settings.local.json, over the project-level .gemini/settings.json.

Guidance

• Check for the existence of .gemini/settings.local.json in the CLI configuration loading process.
• Merge the local configuration with the project-level configuration, giving priority to local settings.
• Ensure that the local configuration file can be safely ignored by version control systems using .gitignore or global ignore settings.
• Consider adding documentation to instruct users on how to use the local configuration file for machine-specific overrides.

Example

// .gemini/settings.json (project-level)
{
  "hooks": {
    "pre-commit": "echo 'Project-level hook'"
  }
}

// .gemini/settings.local.json (local-only)
{
  "hooks": {
    "pre-commit": "echo 'Local hook override'"
  }
}

In this example, the local hook override should take precedence over the project-level hook.

Notes

This solution assumes that the existing configuration loading mechanism can be extended to support the local configuration file. The exact implementation details may vary depending on the current configuration handling code.

Recommendation

Apply a workaround by implementing the configuration merge mechanism, as this will provide the necessary flexibility for users to define local-specific settings without modifying the shared project configuration.