Repository navigation
chore: pin self-review workflow to the canonical dotCMS repo - #4
Conversation
This repo is no longer a fork of wezell/openrouter-code-review-action — it is the canonical home. Point the self-review workflow's trusted-ref pin at itself (v1.0.3 tag SHA) and update the coverage test to assert the canonical owner for the review workflow. The act workflow still pins the wezell ref; update it separately if desired.
Auto Release on Merge cut v1.1.0 from the merged main; follow the 'update the pin on each release' convention and point the self-review workflow at the latest release SHA.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
wezell/openrouter-code-review-action is no longer the source of releases: its main/v1/latest sit at 34ee169 (v1.0.0-era, no github_approval_token input), and it has no release carrying that input. So after the previous two commits the run died earlier still: ##[error]Unable to resolve action `wezell/openrouter-code-review-action@bbe2345...` This repo is canonical and cuts its own releases (auto-release.yml), so point both workflows at bbe2345... (v1.2.0 / v1 / latest), which declares every input the workflows pass, and require the canonical owner in tests. Supersedes the still-open PR #4, which pinned the review workflow to v1.1.0 and left act on wezell.
Updated the action reference to use the latest version.
Both dotbot workflows now use dotCMS/openrouter-code-review-action@latest instead of a frozen SHA: dotCMS owns this repo and cuts every release here (auto-release.yml), so the moving tag is as trusted as a SHA and can never lag an input the workflows pass. - fix the broken `:latest` ref (Actions refs use `@`, not `:`) - point dotbot-act.yml at @latest too, kept in lockstep with the review workflow - restore the coverage/guard tests this branch had deleted and assert the shared @latest pin again - revert the merge-artifact review model change back to deepseek-v4-pro-0813 - teach the actionlint CI step to ignore its unknown-`queue` false positive: concurrency `queue` is valid GitHub syntax, actionlint 1.7.12 predates it
|
dotbot code review:
Change intentionally floats both self-hosted workflows on the canonical @latest tag owned by this repo with test enforcement, and narrowly ignores only the actionlint queue diagnostic. No correctness, security, or atomicity regression introduced by this patch. Tip: comment with "/dotbot address comments" to attempt automated fixes for unresolved review threads. reviewed by dotbot · meta/muse-spark-1.3 · medium |
|
dotbot code review:
The change intentionally floats both self-hosted workflows on the repo-owned Tip: comment with "/dotbot address comments" to attempt automated fixes for unresolved review threads. reviewed by dotbot · ~z-ai/glm-latest · medium |
dotCMS-Machine-User
left a comment
dotCMS-Machine-User
left a comment
There was a problem hiding this comment.
✅ dotbot review: all reviewer models (meta/muse-spark-1.3, ~z-ai/glm-latest) agree — patch is correct.
approved automatically by dotbot
2 participants
What
This repo is no longer a fork of
wezell/openrouter-code-review-action— it is the canonical home. Point the self-review workflow's trusted-ref pin at itself instead of the upstream fork.Changes
.github/workflows/dotbot-review.yml—uses: dotCMS/openrouter-code-review-action@a716ed1…(the v1.0.3 tag SHA), replacing thewezell@d68edbb…pin.tests/test_module_coverage.py— the review-workflow assertion now checksdotCMS/openrouter-code-review-action@; the act-workflow assertion still checkswezell@(act mode is unchanged).Notes
dotbot-act.yml) still pinswezell; update it separately if you want it canonical too.main; this is a follow-up on top of it.🤖 Generated with Zed