Re: Is Git Add Supposed to Work Like This (git 2.50)?
- From
Jeff King <peff@peff.net>
- Date
- Sep 9, 2025, 18:40 UTC
- Message-ID
- <20250909184045.GA1912898@coredump.intra.peff.net>
- In-Reply-To
- <b8df3605-7afe-4121-ae50-095dfd671df9@gmail.com>
On Tue, Sep 09, 2025 at 09:00:34AM -0700, Jon Forrest wrote:
Show 14 quoted lines
> > I guess one could argue either way (though probably not at this point in > > time, as switching behaviors would cause confusion). But one challenge > > with "partial success" like this is that the exit code is binary. If we > > return "0" even though some items were ignored, callers may miss a > > failure. If we return "1" even though some items were added, callers may > > not realize they've mutated the state (and might need to rollback > > depending on what they were trying to accomplish). > > If this were a big deal, which it isn't, I'd suggest a command line > flag that says what to do if there's an invalid file specified on > the command line. One setting of the flag would result in the > current behavior and the other setting would result in all the > invalid file(s) being ignored and the valid file(s) being > handled normally.
Interestingly there are a few --ignore-* options, including --ignore-missing, which I think does what you want. But it only works with --dry-run. I didn't dig into the rationale.
-Peff