feat: add 1Password secrets backend

[khalilgharbaoui]

Summary

• add a 1Password secrets backend with config validation and backend plumbing
• integrate secrets pull/push/status commands and hook backend into sync lifecycle
• exclude auth.json and mcp-auth.json from git sync when using 1Password

Testing

• Not run (not requested)

Related

• Addresses Add secretsBackend option (e.g. 1Password) #34

[gemini-code-assist]

Summary of Changes

Hello @khalilgharbaoui, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a significant security and usability enhancement to opencode-synced by providing an optional 1Password secrets backend. This feature allows users to store and manage their opencode authentication credentials and other sensitive configuration files in 1Password, rather than directly within their git repository. The implementation includes new commands for explicit secrets management, integrates secrets operations into the existing pull/push synchronization lifecycle, and enforces strict exclusion of these sensitive files from git commits when the 1Password backend is active. This change aims to improve the security posture for users handling sensitive opencode data.

Highlights

• 1Password Secrets Backend: Implemented an optional 1Password secrets backend to securely manage opencode authentication tokens and other sensitive files.
• Git Exclusion for Secrets: Automatically excludes auth.json and mcp-auth.json from git synchronization when the 1Password backend is configured, preventing sensitive data from being committed to repositories.
• New Secrets Commands: Added dedicated commands (secrets-pull, secrets-push, secrets-status) for direct interaction with the 1Password backend.
• Integrated Sync Lifecycle: The secrets backend is seamlessly integrated into the existing sync workflow, performing pulls after sync-pull and pushes before sync-push.
• Robust Configuration & Validation: Implemented new configuration types and validation logic for the 1Password backend, ensuring proper setup and error handling.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a 1Password secrets backend, a significant and well-implemented feature. While the code is well-structured and considers security aspects, a medium-severity race condition was identified in how secret files are moved to their final destination, potentially exposing them to other users on the system briefly. This should be addressed by ensuring restricted permissions are applied before the files are moved to a publicly accessible directory. Additionally, there are suggestions for improving code clarity, consistency, and maintainability, such as simplifying a complex type definition, making type signatures more accurate, and refactoring duplicated logic.

[jules-relay]

🤖 Review Jules Relay

I found 1 Gemini suggestion so far.

Type /relay batch to send all suggestions to Jules.