{"thread":{"id":"62741","subject":"Add --untracked-is-dirty option to git describe","startedAt":"2025-01-05T12:12:29Z","lastAt":"2025-01-05T12:12:29Z","messageCount":1,"participants":["Ross Goldberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"509926","messageId":"CAAEcvMp8obN4b-zpG4wUtt7-O17j4mEMSHLbu0wZ0XWUKKn6Tw@mail.gmail.com","threadId":"62741","inReplyTo":null,"subject":"Add --untracked-is-dirty option to git describe","fromName":"Ross Goldberg","fromEmail":"ross.goldberg@gmail.com","sentAt":"2025-01-05T12:12:14Z","receivedAt":"2025-01-05T12:12:29Z","isPatch":false,"sender":{"key":"ross.goldberg@gmail.com","avatar":null},"body":"Could you possibly add an option like --untracked-is-dirty to git\ndescribe? (the name can obviously be changed to whatever you think is\nbest)\n\nFrom what I gather, git describe --dirty[=<mark>] applies to deleted &\nmodified tracked files, regardless if the change is staged or not, but\nonly to new files if they are staged. If an untracked file that is not\nignored by git exists in the repo, it doesn't seem to trigger\n--dirty[=<mark>]. Please let me know if my understanding is incorrect.\n\nMy proposed --untracked-is-dirty option would make untracked files\nthat aren't ignored by git trigger --dirty[=<mark>]. It would only be\nvalid if --dirty[=<mark>] has been specified. If you don't want to add\nin a whole new option, you could have an alternate syntax for dirty\nthat activates this proposed behavior, maybe --dirty:[<mark>] (the =\nhas been replaced by a : to activate considering untracked non-ignored\nfiles as dirty)\n\nAre there any other categories of file statuses that someone might\nwant to be considered dirty? If so, then any solution should take them\ninto account, too.\n\nThanks.\n"}]}