{"thread":{"id":"61689","subject":"Usage of `-u` flag in `git status` cli","startedAt":"2024-06-28T04:21:17Z","lastAt":"2024-06-28T04:21:17Z","messageCount":1,"participants":["Ajith Sakharia"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"497785","messageId":"CA+8M_AZTtqSU7ugZ-w8yyOKeP+opambD08DSOGko8akL_CXQqQ@mail.gmail.com","threadId":"61689","inReplyTo":null,"subject":"Usage of `-u` flag in `git status` cli","fromName":"Ajith Sakharia","fromEmail":"ajithk.sakharia@gmail.com","sentAt":"2024-06-28T04:21:04Z","receivedAt":"2024-06-28T04:21:17Z","isPatch":false,"sender":{"key":"ajithk.sakharia@gmail.com","avatar":null},"body":"Hello,\nI have recently been working on some performance initiatives on git\nstatus cli and its usages. As a result I found something confusing and\nwanted a confirmation on the expected behaviour.\nBased on documentation the status cli has a `-u/--untracked-files flag\nwith 3 potential values `no` `normal` and `all`. The `true`is expected\nto be treated as `normal`. But from my experiments it looks like there\nis a difference in `git status --untracked-files` vs `git status\n--untracked-files=true` (notice the existence of `true` being\nexplicitly mentioned), where the `git status --untracked-files` gets\ntreated as `git status --untracked-files=all` as suppose to `normal`.\nAdditionally, `--untracked-files=all` doesn't seem to use the benefits\nof `fsmonitor` and `untracked cache`. From some additional\ninvestigations the impact seems to also scale to git plugins across\ntooling like vscode, warp etc that use the `-u` flag as part of their\nsyncing logic.\nCould you please help me understand if this is expected ?\nRegards,\nAjith K S\n"}]}