Skip to content

fix(review): align attribution and consolidate GitHub reviews#4

Merged
whhe merged 3 commits into
mainfrom
fix-review-workflow-attribution
Jul 16, 2026
Merged

fix(review): align attribution and consolidate GitHub reviews#4
whhe merged 3 commits into
mainfrom
fix-review-workflow-attribution

Conversation

@whhe

@whhe whhe commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Summary

Make review provenance explicit and avoid duplicate GitHub summary artifacts while retaining the published OpenCode image for the self-review workflow.

Changes

  • Identify generated comments as coming from whhe/code-review-bot and display the active skill fingerprint.
  • Publish the complete summary as the final GitHub APPROVE or REQUEST_CHANGES review body when supported.
  • Fall back to an issue comment when the final review cannot be submitted.
  • Read paginated GitHub review bodies so hidden fingerprint metadata remains available for incremental deduplication.
  • Preserve compatibility with existing platform adapters and custom review publishers.
  • Keep the self-review workflow on whhe/code-review-bot:opencode.
  • Remove presentation-only assertions while retaining functional behavior and metadata coverage.

Motivation

The previous workflow could publish both a complete summary comment and a separate generic “Code review found new issues.” review. Consolidating them produces one authoritative review result without assuming a fixed review-skill URL or breaking extension implementations.

Validation

  • uv run pytest tests -q — 219 passed
  • uv run ruff check src tests --ignore UP047
  • Ruff format checks for all modified Python files
  • Parsed .github/workflows/code-review.yml with PyYAML
  • git diff --check

whhe added 2 commits July 16, 2026 20:26
fix:
- Build the OpenCode review image from the exact pull request head
- Attribute review comments to the bot and show the active skill fingerprint

test:
- Remove presentation-only assertions from repository tests

docs:
- Document the development-image self-review workflow
fix:
- Pass docker/Dockerfile explicitly when building the OpenCode review image
@github-actions

Copy link
Copy Markdown

Code Review

Low risk. Self-review workflow correctly builds from PR source with same-repo guard and persist-credentials:false. One minor test coverage gap from a deleted negative-case assertion.

Severity: Critical 0 / High 0 / Medium 0 / Low 1
Inline comments posted: 1

Generated by whhe/code-review-bot · Skill fingerprint: 43b5df0c

Comment thread tests/test_review_publisher.py

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review found new issues.

fix:
- Publish the full summary as the GitHub approval decision body
- Preserve metadata discovery and extension compatibility
- Fall back to issue comments when review submission fails

ci:
- Restore the published OpenCode image for self-review

test:
- Cover review consolidation, fallback, pagination, and legacy contracts
@whhe whhe changed the title fix(review): align self-review image and attribution fix(review): align attribution and consolidate GitHub reviews Jul 16, 2026
Comment thread src/code_review_bot/review/orchestrator.py
@github-actions

Copy link
Copy Markdown

Code Review

Low risk: well-structured consolidation of GitHub review body with strong backward compatibility. One medium concern: unprotected fallback publish_summary call. Existing open thread on missing negative-case test remains valid.

Severity: Critical 0 / High 0 / Medium 1 / Low 0
Inline comments posted: 1

Skill: code-review v43b5df0c

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review found new issues.

@whhe
whhe merged commit 28236e5 into main Jul 16, 2026
1 check 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