As of Oct 2020 Homebrew no longer creates shallow clones when being installed, and as of Dec 2020 updating existing shallow clones is not allowed either.
(This makes the original question about silencing the warning moot).
If a shallow clone is configured, a message containing text like the below will be shown:
Error:
homebrew-core is a shallow clone.
homebrew-cask is a shallow clone.
To `brew update`, first run:
git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow
git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask fetch --unshallow
It is now required to perform the unshallow process by running the git
command(s) in the error message.
Note: This process may take a long time to complete without providing feedback.
For some details about the motivation for this change, see this discussion on Homebrew's GitHub page, specifically:
There are two major downsides of shallow cloning:
- It places a massive computation burden on GitHub's servers, which have to?dynamically?compute a fresh delta between what you have and the latest commit, on every?
brew update
. (With full clones, GitHub can simply send you all the commits that happened after your last pull, and your local Git client takes care of the rest.)
- Because of [1], it makes it far more likely that GitHub will rate-limit Homebrew operations, which will make it suck for everyone.
--gromgit Dec 5, 2020, 12:29 AM EST
And also this additional text added to the error message:
This restriction has been made on GitHub's request because updating shallow
clones is an extremely expensive operation due to the tree layout and traffic of
Homebrew/homebrew-core and Homebrew/homebrew-cask.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…