| commit | c75662bfc963fb3e776e4a863bbb726819352cfd | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Wed, 24 Apr 2024 16:14:59 +0000 (24 16:14 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 24 Apr 2024 17:46:03 +0000 (24 10:46 -0700) | ||
| tree | 42855ff0cc6fed634746ccca59129d27d3bfce28 | treesnapshot (tar.gz zip) |
| parent | 12c2ee5fbd1ab0f0fcf7ca37c613d438db52821d | commitdiff |
maintenance: running maintenance should not stop on errors
In https://github.com/microsoft/git/issues/623, it was reported that
maintenance stops on a missing repository, omitting the remaining
repositories that were scheduled for maintenance.
This is undesirable, as it should be a best effort type of operation.
It should still fail due to the missing repository, of course, but not
leave the non-missing repositories in unmaintained shapes.
Let's use `for-each-repo`'s shiny new `--keep-going` option that we just
introduced for that very purpose.
This change will be picked up when running `git maintenance start`,
which is run implicitly by `scalar reconfigure`.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In https://github.com/microsoft/git/issues/623, it was reported that
maintenance stops on a missing repository, omitting the remaining
repositories that were scheduled for maintenance.
This is undesirable, as it should be a best effort type of operation.
It should still fail due to the missing repository, of course, but not
leave the non-missing repositories in unmaintained shapes.
Let's use `for-each-repo`'s shiny new `--keep-going` option that we just
introduced for that very purpose.
This change will be picked up when running `git maintenance start`,
which is run implicitly by `scalar reconfigure`.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/gc.c | diffblobblamehistory | |
| t/t7900-maintenance.sh | diffblobblamehistory |