Skip to content

ci: replace the platform parity review with the apify-factory review - #117

Merged
Pijukatel merged 7 commits into
masterfrom
claude/review-references
Nov 3, 2026
Merged

Pijukatel merged 7 commits into
masterfrom
claude/review-references

Conversation

@Pijukatel

@Pijukatel Pijukatel commented Nov 3, 2026 •

Copy link
Copy Markdown
Collaborator

Pull requests are reviewed against the real platform by the apify-factory review: .github/review-references.yaml names apify-core, apify-worker and apify-containerd-proxy and what to compare, and the stub calls the public reusable workflow. The separate platform parity workflow is removed.

Gathered only for pull requests by Apify members; the stub stays pinned to the ai-developer branch that drafts the references until it lands on main.

`.github/review-references.yaml` names apify-core, apify-worker and
apify-containerd-proxy as the repositories the apify-factory review compares
a pull request with, and what to compare, drawn from the platform parity
review's instructions. The stub calls the public reusable workflow directly,
pinned to the ai-developer branch that drafts the feature, to compare the two
reviews side by side.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_017ocuAL43YR6VPaBRrRfBbL
The apify-factory review now compares a pull request with apify-core,
apify-worker and apify-containerd-proxy through `.github/review-references.yaml`,
so the separate platform parity workflow and its Managed Agent session are no
longer needed.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_017ocuAL43YR6VPaBRrRfBbL
@Pijukatel
Pijukatel requested a review from mtrunkat as a code owner November 3, 2026 14:53
@Pijukatel

Copy link
Copy Markdown
Collaborator Author

Flaky tests will be investigated on their own.

@Pijukatel
Pijukatel merged commit 26058e1 into master Nov 3, 2026
37 of 40 checks passed
@Pijukatel
Pijukatel deleted the claude/review-references branch November 3, 2026 15:55
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.

2 participants