Skip to content

docs: refresh diff_collect.rs module summary to match its coverage #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cargo-affected-bot wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: refresh diff_collect.rs module summary to match its coverage #49

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
430f92f
docs: refresh diff_collect.rs module summary to match its coverage
cargo-affected-bot Jun 8, 2026
7a44b44
docs: say 'dropped out of the object database', not 'diverged'
cargo-affected-bot Aug 3, 2026
a3cb292
docs: drop the missing-sha clause this file has no scenario for
cargo-affected-bot Aug 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions tests/functional/diff_collect.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,16 @@
//! at their original sha.
//!
//! This file exercises the headline guarantee — multiple shas can coexist
//! in `test_regions` for the same fingerprint after `--diff` — plus the
//! two error paths the project's "fail loudly" stance demands: no prior
//! collect, and a stored sha no longer reachable from HEAD.
//! in `test_regions` for the same fingerprint after `--diff` — along with
//! the row-maintenance and selection behaviors built on it: re-anchoring
//! only affected tests, accumulating distinct shas across rounds, pruning
//! deleted/renamed tests while keeping merely-ignored ones, recovering from
//! an all-phantom selection, and short-circuiting a clean tree. A few `run`
//! cases live here too, since they exercise the multi-sha state `--diff`
//! creates: a sibling sha is reachable rather than fatal (#9), and a
//! selection spanning several shas stays narrow instead of widening to the
//! whole suite.
//! The one hard error covered is the "fail loudly" no-prior-collect path.

use crate::{
cargo_affected, combined_output, git, git_head, init_git_with_initial_commit, replace_in_file,
Expand Down
Loading