Update opencode config filename - #635
Conversation
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @x-n2o on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment |
|
@x-n2o is attempting to deploy a commit to the warpdotdev Team on Vercel. A member of the Team first needs to authorize it. |
|
Every PR must be linked to a same-repo issue before Oz can review it. Next step: open or find a same-repo issue describing this change, then link it to this PR by adding See the contribution guidelines for the full readiness model. Powered by Oz |
There was a problem hiding this comment.
Every PR must be linked to a same-repo issue before Oz can review it.
Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /warp-agent-review to re-trigger review.
See the contribution guidelines for the full readiness model.
Powered by Oz
|
@cla-bot check |
|
The cla-bot has been summoned, and re-checked this pull request! |
|
|
Summary
Updated the OpenCode configuration filename reference in the documentation from
opencode.jsontoopencode.jsoncto match support for JSON with comments.Related issues
Closes #636
Validation
Verified that the documentation file
src/content/docs/agents/cli-agents/opencode.mdxcorrectly reflects theopencode.jsoncfilename used by the plugin configuration.Screenshots
None
Follow-ups
None