On Sun, Sep 12 2021, Derrick Stolee via GitGitGadget wrote: > +# NEEDSWORK: This documents current behavior, but is not a desirable > +# behavior (untracked files are handled differently than tracked). I wonder if a test_expect_failure test would be better for the thing that is the desired behavior, but maybe we don't know what the CLI UI for that would look like yet. > +test_expect_success 'add outside sparse cone' ' > + init_repos && > + > + run_on_sparse mkdir folder1 && > + run_on_sparse ../edit-contents folder1/a && > + run_on_sparse ../edit-contents folder1/newfile && > + test_sparse_match test_must_fail git add folder1/a && > + test_i18ngrep "Disable or modify the sparsity rules" sparse-checkout-err && Just "grep" is preferred over "test_i18ngrep" now, the GETTEXT_POISON went away.
