The self-push rule in one place: a commit created by `atomic git push` carries the target view's Merkle state, so if that view already has the state, the commit adds nothing. Shared by [`should_skip_self_push`] and [`incremental_import_skips`] so the real import and the `--dry-run` forecast can never disagree on it.
(
trailer: &PushTrailer,
target_view: &str,
known_states: &HashSet<Merkle>,
)
| 590 | /// [`incremental_import_skips`] so the real import and the `--dry-run` forecast |
| 591 | /// can never disagree on it. |
| 592 | fn self_push_state_known( |
| 593 | trailer: &PushTrailer, |
| 594 | target_view: &str, |
| 595 | known_states: &HashSet<Merkle>, |
| 596 | ) -> bool { |
| 597 | trailer.view == target_view && known_states.contains(&trailer.state) |
| 598 | } |
| 599 | |
| 600 | /// Whether an incremental import would skip the git commit identified by `sha` |
| 601 | /// with the given commit `message`, for a target view that already contains |
no test coverage detected