feat: adicionar workflows OpenCode com OmniRoute e remover OpenHands#79
Conversation
Co-Authored-By: Afonso Dutra Nogueira Filho <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Qodana Community for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/[email protected]
with:
upload-result: trueContact Qodana teamContact us at [email protected]
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| if: | | ||
| contains(github.event.comment.body, '/oc') || | ||
| contains(github.event.comment.body, '/opencode') |
There was a problem hiding this comment.
🔍 Comment-triggered workflow lost author authorization gating
The deleted openhands-resolver.yml restricted comment-triggered runs to users with author_association of OWNER, COLLABORATOR, or MEMBER. The replacement opencode.yml triggers for any user who comments /oc or /opencode — there is no author_association check in the if condition at .github/workflows/opencode.yml:11-13. Whether the downstream anomalyco/opencode/github@latest action enforces its own authorization is unknown from this repo's context. If it does not, this is a significant behavioral regression in access control. Worth confirming with the action's documentation.
Was this helpful? React with 👍 or 👎 to provide feedback.
| | `opencode.yml` | issue_comment / pull_request_review_comment | OpenCode com OmniRoute (chat) | | ||
| | `opencode-auto-fix.yml` | issue label | OpenCode com OmniRoute (fix-me) | |
There was a problem hiding this comment.
🔍 Trigger Conditions table in WORKFLOWS.md not updated for new workflows
The .agents/WORKFLOWS.md:81-89 Trigger Conditions table still only lists the original five workflows and does not mention opencode.yml or opencode-auto-fix.yml. Meanwhile, .agents/TOOLS.md:27-28 was updated to list both new workflows. This creates an inconsistency between two agent documentation files that are both loaded as context for AI agents working on this repo. A follow-up commit should add the new triggers to WORKFLOWS.md to keep agent context consistent.
Was this helpful? React with 👍 or 👎 to provide feedback.
| issue_comment: | ||
| types: [created] | ||
| pull_request_review_comment: | ||
| types: [created] |
There was a problem hiding this comment.
🔍 Old workflow's reusable workflow_call and pull_request_review triggers were dropped
The deleted openhands-resolver.yml supported workflow_call (making it reusable from other workflows) and pull_request_review: types: [submitted] as a trigger. Neither new workflow includes these triggers. If any other workflow in the repo or organization called the old workflow via workflow_call, those callers will now fail silently (the job simply won't exist). The pull_request_review trigger also means review-body commands (e.g. mentioning /oc in a PR review submission, as opposed to a review comment) will no longer trigger the agent. This may be intentional simplification but is worth confirming.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
|
||
| jobs: | ||
| opencode: | ||
| if: github.event.label.name == 'fix-me' |
There was a problem hiding this comment.
📝 Info: Support for fix-me-experimental label was silently dropped
The old openhands-resolver.yml handled both fix-me and fix-me-experimental labels (the latter installed an experimental version of the agent). The new opencode-auto-fix.yml:11 only checks for fix-me. If any existing issues or documentation reference the fix-me-experimental label, labeling with it will no longer trigger any workflow. This appears intentional given the tool change, but any existing process documentation or contributor guides mentioning this label should be updated.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
User devin-ai-integration[bot] does not have write permissions |
|
User devin-ai-integration[bot] does not have write permissions |
|
User devin-ai-integration[bot] does not have write permissions |
Co-Authored-By: Afonso Dutra Nogueira Filho <[email protected]>
|
1 participant
All Submissions:
Changes to Core Features:
Description
This PR replaces the OpenHands workflow with OpenCode workflows using the OmniRoute API.
Added
opencode.yml: triggers on issue comments and PR review comments (/oc,/opencode).opencode-auto-fix.yml: triggers when an issue or PR is labeledfix-me.opencode.json: project-level configuration for OpenCode with the OmniRoute provider.Removed
.github/workflows/openhands-resolver.yml(no longer needed).Configuration
OMNIROUTE_API_KEYGitHub secret.opencode.jsonuses environment variables to avoid committing secrets.Notes
.agents/TOOLS.mdandMetarDecoder.slnwere updated to reflect the new workflows./closes
Link to Devin session: https://app.devin.ai/sessions/f862be50b6ad41bfa3bb93c39e8a89a6
Requested by: @afonsoft