Skip to content

fix(ci): use OPENCODE_PAT in test-writer to trigger downstream workflows#448

Merged
github-actions[bot] merged 1 commit intodevfrom
ci/fix-test-writer-pat-token
Apr 11, 2026
Merged

fix(ci): use OPENCODE_PAT in test-writer to trigger downstream workflows#448
github-actions[bot] merged 1 commit intodevfrom
ci/fix-test-writer-pat-token

Conversation

@MichaelFisher1997
Copy link
Copy Markdown
Collaborator

Summary

  • Replace all github.token references in opencode-test-writer.yml with secrets.OPENCODE_PAT so that PRs created by the bot actually trigger build.yml and opencode-pr.yml
  • Reduce opencode-audit.yml timeout from 60 → 20 minutes

Why

GitHub's GITHUB_TOKEN cannot trigger other workflows — this is a deliberate security restriction. PR #447 was created but neither build.yml nor opencode-pr.yml fired. The audit and visual-test workflows already use OPENCODE_PAT for the same reason.

GITHUB_TOKEN cannot trigger other workflows (GitHub security policy).
Replace all github.token refs with secrets.OPENCODE_PAT so that PRs
created by the test-writer trigger build.yml and opencode-pr.yml.

Also reduce audit workflow timeout from 60 to 20 minutes.
@github-actions github-actions bot added documentation Improvements or additions to documentation ci labels Apr 11, 2026
@github-actions
Copy link
Copy Markdown
Contributor

📋 Summary

PR #448 is a CI configuration fix that replaces github.token with secrets.OPENCODE_PAT in opencode-test-writer.yml (6 occurrences) and reduces the audit workflow timeout from 60 to 20 minutes. No linked issues. This is a well-scoped, minimal fix addressing GitHub's deliberate security restriction where GITHUB_TOKEN cannot trigger downstream workflows.

📌 Review Metadata


🔴 Critical Issues (Must Fix - Blocks Merge)

None identified.

⚠️ High Priority Issues (Should Fix)

None identified.

💡 Medium Priority Issues (Nice to Fix)

None identified.

ℹ️ Low Priority Suggestions (Optional)

None identified.


📊 SOLID Principles Score

Principle Score Notes
Single Responsibility N/A CI workflow files, not applicable
Open/Closed N/A CI workflow files, not applicable
Liskov Substitution N/A CI workflow files, not applicable
Interface Segregation N/A CI workflow files, not applicable
Dependency Inversion N/A CI workflow files, not applicable
Average N/A

🎯 Final Assessment

Overall Confidence Score: 95%

How to interpret:

  • 0-30%: Major concerns, do not merge without significant rework
  • 31-60%: Moderate concerns, several issues need addressing
  • 61-80%: Minor concerns, mostly ready with some fixes
  • 81-100%: High confidence, ready to merge or with trivial fixes

Confidence Breakdown:

  • Code Quality: 100% (CI config is syntactically correct)
  • Completeness: 95% (all github.token refs replaced; timeout reduction is reasonable)
  • Risk Level: 100% (minimal risk - CI-only changes)
  • Test Coverage: N/A (no code changes to test)

Merge Readiness:

  • All critical issues resolved
  • No security concerns (this PR improves security by using the proper PAT)
  • Changes are well-documented in PR body
  • Matches existing pattern in other workflow files (opencode-audit.yml, visual-test.yml)

Verdict:

MERGE — This is a minimal, well-understood CI fix that follows established patterns. The change to use OPENCODE_PAT resolves the workflow triggering issue and aligns with other workflows in the repo. The timeout reduction from 60 to 20 minutes is reasonable given the audit task scope.


{
  "reviewed_sha": "5be5422417fcba25ca7a3fb95e9e8bd3bf6d59d8",
  "critical_issues": 0,
  "high_priority_issues": 0,
  "medium_priority_issues": 0,
  "overall_confidence_score": 95,
  "recommendation": "MERGE"
}

New%20session%20-%202026-04-11T13%3A01%3A31.816Z
opencode session  |  github run

@github-actions github-actions bot merged commit edd1ec4 into dev Apr 11, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant