Post-rebase git hook not triggered

[tschaffter]

vscode@ade7130aff68:/workspaces/challenge-registry$ git fetch upstream
remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 1 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (1/1), 572 bytes | 572.00 KiB/s, done.
From https://github.com/Sage-Bionetworks/challenge-registry
   4a9a0f3..80fe0ca  main       -> upstream/main

vscode@ade7130aff68:/workspaces/challenge-registry$ git rebase upstream/main
Successfully rebased and updated refs/heads/main.

[tschaffter]

Added to Sprint 22.10. Get a final answer regarding the behavior of post-rebase hooks.

[tschaffter]

• Rebasing currently does trigger yarn install --immutable.
• The git hook post-checkout is called when rebasing.
• The git hook post-rewrite is not called in my "simple" example.

The reason post-rewrite is not called may be because my rebase are fast-forward merge that do not involve rewrites. See this comment:

You are not rewriting any commits; you are fast-forwarding; so basically your branch just points to another commit. None of the commits are rewritten.

I was able to trigger the post-rewrite hook after resolving a rebase that had a conflict.

Conclusion

I need to keep the post-rewrite hook in case a conflict arise in one of the files that define package version.