Skip to content

chore: pin self-review workflow to the canonical dotCMS repo - #4

Open
wezell wants to merge 3 commits into
mainfrom
chore/pin-self-review-to-canonical
Open

chore: pin self-review workflow to the canonical dotCMS repo#4
wezell wants to merge 3 commits into
mainfrom
chore/pin-self-review-to-canonical

Conversation

@wezell

@wezell wezell commented Sep 4, 2026

Copy link
Copy Markdown
Member

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.ymluses: dotCMS/openrouter-code-review-action@a716ed1… (the v1.0.3 tag SHA), replacing the wezell@d68edbb… pin.
  • tests/test_module_coverage.py — the review-workflow assertion now checks dotCMS/openrouter-code-review-action@; the act-workflow assertion still checks wezell@ (act mode is unchanged).

Notes

🤖 Generated with Zed

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.
Comment thread .github/workflows/dotbot-review.yml Outdated
v1.1.0 is an annotated tag, so the tag ref returns the tag object SHA
(a2b9517), which does not resolve as a uses: ref. Peel it to the commit
SHA (aa372f5) the tag points at.
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

dotbot code review:

  • Reviewer: meta/muse-spark-1.3 (medium)
  • Overall: patch is correct
  • New findings this run: 0
  • Prior unresolved dotbot findings still relevant: 0
  • Active findings total: 0

The incremental change replaces the annotated tag-object SHA with its peeled commit SHA, which resolves the prior pin issue and matches the v1/latest tag target.

Tip: comment with "/dotbot address comments" to attempt automated fixes for unresolved review threads.

reviewed by dotbot · meta/muse-spark-1.3 · medium

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

dotbot code review:

  • Reviewer: ~z-ai/glm-latest (medium)
  • Overall: patch is correct
  • New findings this run: 0
  • Prior unresolved dotbot findings still relevant: 0
  • Active findings total: 0

The incremental change replaces the tag-object SHA with the peeled commit aa372f5, resolving the prior finding. The pin now points to a real commit SHA consistent with the workflow's documented convention.

Tip: comment with "/dotbot address comments" to attempt automated fixes for unresolved review threads.

reviewed by dotbot · ~z-ai/glm-latest · medium

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