[waleedlatif1]

Summary

• Fix unnecessary full CI on narrow PR updates after staging advances: the old event base can be disconnected in a shallow checkout even when its commit exists.
• Attribute against the actual tested GitHub merge's target parent after verifying the merge ref, triggering SHA, and two-parent shape. Retain full fallback when attribution is uncertain.
• Preserve manual-base and push behavior; planner/configuration changes, including this PR, still run full CI.

Type of Change

• Bug fix

Testing

• 62 real Git/Turbo cases, including shallow multi-commit PRs, upstream changes, and invalid checkout identities.
• Regressions demonstrated red before implementation; ref, SHA, parent-shape, and parent-selection mutations independently go red.
• Root bun run test, lint, type-check, all audits, artifact generators, block-registry check, and actionlint.
• Cleanup and test-audit; no retries, timeout changes, or coverage reductions.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 3, 2026 11:30pm UTC

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

PR checks now compare the tested GitHub merge with its first parent instead of relying on the event’s potentially stale base SHA.

• Pull request CI scopes checks from the target parent in its tested merge.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Valid comparison SHA] --> B{Pull request?}
  B -->|Yes| C{Merge ref, SHA and parents match?}
  C -->|Yes| D[Use first parent]
  C -->|No| F[Run every check]
  B -->|No| E[Use existing merge-base logic]
  D --> G[Compare files and query affected tasks]
  E --> G
  G -->|Success| H[Run selected checks]
  G -->|Missing history or attribution error| F

Loading

_{Reviews (1) · Last reviewed commit: "fix(ci): attribute pull requests against..." · Reviewed by Greptile}