Skip to content

fix: let OpenCode access private SecAgent repositories - #20

Merged
PANDAJSR merged 1 commit into
masterfrom
fix/opencode-cross-repo-token
Sep 4, 2026
Merged

fix: let OpenCode access private SecAgent repositories#20
PANDAJSR merged 1 commit into
masterfrom
fix/opencode-cross-repo-token

Conversation

@PANDAJSR

@PANDAJSR PANDAJSR commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • expose SECTL_SECAGENT_GITHUB_TOKEN to OpenCode as GH_TOKEN for cross-repository GitHub CLI and Git access
  • verify access to the private SECTL/secagent-official-relay repository before starting the agent
  • configure Git credentials from the cross-repository token
  • explicitly instruct the agent to inspect and submit fixes to related private SecAgent repositories while retaining GITHUB_TOKEN for the primary issue event

Root cause

The workflow used the cross-repository secret only in the discovery step. The actual OpenCode step received only ${{ github.token }}, which is scoped to SECTL/SecAgent. Consequently, the agent could list public repositories but could not see or clone private repositories such as SECTL/secagent-official-relay.

Validation

  • configured SECTL_SECAGENT_GITHUB_TOKEN on SECTL/SecAgent
  • confirmed the underlying token can access SECTL/secagent-official-relay
  • workflow YAML parsed successfully
  • git diff --check passed

@PANDAJSR
PANDAJSR merged commit a011d58 into master Sep 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant