Why the daemon must not start under the current configuration, if it must not. The daemon is opt-in only (RFC §11.2 rule 7): it is off unless `[git.shim.watch] enabled = true` is explicitly recorded, which is also how CI and containers stay off — they get the same disabled default as everywhere else, and only an explicit per-repository opt-in starts the daemon there.
(&self)
| 673 | /// disabled default as everywhere else, and only an explicit |
| 674 | /// per-repository opt-in starts the daemon there. |
| 675 | pub fn startup_refusal(&self) -> Option<&'static str> { |
| 676 | if self.enabled { |
| 677 | return None; |
| 678 | } |
| 679 | Some( |
| 680 | "the shim watch daemon is disabled (set [git.shim.watch] enabled = true to opt in; \ |
| 681 | command boundaries fully reconcile without it)", |
| 682 | ) |
| 683 | } |
| 684 | } |
| 685 | |
| 686 | impl Default for ShimWatchConfig { |