Skip to content

Conversation

joseph-sentry
Copy link
Contributor

Check if the merge commit sha is equal to the sha of the head of the PR because in that case we should also move the commits on the PR to the base branch of the PR.

@codecov-notifications
Copy link

codecov-notifications bot commented Aug 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link

codecov bot commented Aug 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.18%. Comparing base (b911b8c) to head (6b1d1ef).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #388      +/-   ##
==========================================
- Coverage   94.18%   94.18%   -0.01%     
==========================================
  Files        1255     1255              
  Lines       46308    46311       +3     
  Branches     1455     1455              
==========================================
+ Hits        43615    43617       +2     
- Misses       2388     2389       +1     
  Partials      305      305              
Flag Coverage Δ
workerintegration 61.44% <33.33%> (-0.01%) ⬇️
workerunit 90.77% <100.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

codspeed-hq bot commented Aug 8, 2025

CodSpeed Performance Report

Merging #388 will not alter performance

Comparing joey/fix (904eb50) with main (5a06654)1

Summary

✅ 9 untouched benchmarks

Footnotes

  1. No successful run was found on main (ce3f410) during the generation of this report, so 5a06654 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

Copy link
Collaborator

@michelletran-codecov michelletran-codecov left a comment

Choose a reason for hiding this comment

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

Check if the merge commit sha is equal to the sha of the head of the PR because in that case we should also move the commits on the PR to the base branch of the PR.

What's the context for this change? The rebased changes will have a different SHA, so moving these commits to the base branch will cause a mismatch with commit SHA and the actual commit on the main branch.

@@ -420,17 +420,34 @@ def update_pull_commits(
return {"soft_deleted_count": deleted_count, "merged_count": merged_count}

def was_squash_via_merge_commit(self, repository_service, pull_dict):
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: can you also annotate the types of this function?

@joseph-sentry
Copy link
Contributor Author

What's the context for this change? The rebased changes will have a different SHA, so moving these commits to the base branch will cause a mismatch with commit SHA and the actual commit on the main branch.

There's a case where the experiment was failing because the head sha and merge commit sha were equivalent. The previous logic in the experiment would count that as a squash, because it was only checking the # of parents, but the previous logic was correctly detecting that as not a squash merge.

Check if the merge commit sha is equal to the sha of the head of
the PR because in that case we should also move the commits on the PR to the
base branch of the PR.
Copy link
Collaborator

@michelletran-codecov michelletran-codecov left a comment

Choose a reason for hiding this comment

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

Seems low risk given the feature flag. 👍

@joseph-sentry joseph-sentry added this pull request to the merge queue Aug 11, 2025
Merged via the queue into main with commit aff0994 Aug 11, 2025
39 checks passed
@joseph-sentry joseph-sentry deleted the joey/fix branch August 11, 2025 21:05
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