# commit --strict feature request 4 messages from 2010-03-23 to 2010-03-27. Participants: Dario Bertini, Tim Mazid, Tay Ray Chuan. Thread: https://gitlist.dev/t/23153 ## Dario Bertini, 2010-03-23 17:47 Subject: commit --strict feature request Message-ID: <4BA8FEA4.60504@gmail.com> URL: https://gitlist.dev/e/4BA8FEA4.60504%40gmail.com ``` Hi, i usually use bzr, and today i was searching for a commit --strict equivalent in git... i asked around and it seems there isn't one, so i'm writing this. basically, by doing commit --strict it refuses to commit if there are untracked (and thus not ignored) files in the tree, this helps against forgetting to add new files (actually i find it so useful that i've even changed commit to be an alias to commit --strict in my bzr aliases ) greetings ``` ## Tim Mazid, 2010-03-24 01:10 Subject: RE: commit --strict feature request Message-ID: URL: https://gitlist.dev/e/SNT124-W659C1D09B747F338E04DF4C4250%40phx.gbl In-Reply-To: <4BA8FEA4.60504@gmail.com> ``` > Date: Tue, 23 Mar 2010 18:47:16 +0100 > From: berdario@gmail.com > To: git@vger.kernel.org > Subject: commit --strict feature request > > Hi, i usually use bzr, and today i was searching for a commit --strict > equivalent in git... i asked around and it seems there isn't one, so i'm > writing this. > > basically, by doing commit --strict it refuses to commit if there are > untracked (and thus not ignored) files in the tree, this helps against > forgetting to add new files (actually i find it so useful that i've even > changed commit to be an alias to commit --strict in my bzr aliases ) > > > greetings > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Hi, I think (someone correct me if I'm wrong) that being able to commit only part of the changes you made at a time is one of the major points of git (at least for me, anyway), so such a feature might go against the whole design. Also, what you could use is 'git commit -v', which allows you to review all the changes you are commiting, and allows you to write a better commit message anyway, as you can look at the changes, instead of going from memory. Another option might be to use a gui, such as 'git gui', which gives you a clear visual of what files have unstaged changes. Hope that helps until somebody competent replies. Tim. _________________________________________________________________ Browse profiles for FREE! Meet local singles online. http://clk.atdmt.com/NMN/go/150855801/direct/01/ ``` ## Tim Mazid, 2010-03-24 01:14 Subject: RE: commit --strict feature request Message-ID: URL: https://gitlist.dev/e/SNT124-W65458CD48BBB9A6A831FDEC4250%40phx.gbl In-Reply-To: ``` > From: timmazid@hotmail.com > To: berdario@gmail.com; git@vger.kernel.org > Subject: RE: commit --strict feature request > Date: Wed, 24 Mar 2010 12:10:06 +1100 > > >> Date: Tue, 23 Mar 2010 18:47:16 +0100 >> From: berdario@gmail.com >> To: git@vger.kernel.org >> Subject: commit --strict feature request >> >> Hi, i usually use bzr, and today i was searching for a commit --strict >> equivalent in git... i asked around and it seems there isn't one, so i'm >> writing this. >> >> basically, by doing commit --strict it refuses to commit if there are >> untracked (and thus not ignored) files in the tree, this helps against >> forgetting to add new files (actually i find it so useful that i've even >> changed commit to be an alias to commit --strict in my bzr aliases ) >> >> >> greetings >> -- >> To unsubscribe from this list: send the line "unsubscribe git" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > Hi, > > I think (someone correct me if I'm wrong) that being able to commit only part of the changes you made at a time is one of the major points of git (at least for me, anyway), so such a feature might go against the whole design. > > Also, what you could use is 'git commit -v', which allows you to review all the changes you are commiting, and allows you to write a better commit message anyway, as you can look at the changes, instead of going from memory. > > Another option might be to use a gui, such as 'git gui', which gives you a clear visual of what files have unstaged changes. > > Hope that helps until somebody competent replies. > > Tim. > > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Oh, and I just realised, 'git commit' does actually show you a 'git status' (by default in v1.7.0) when you write your message anyway, so you don't even need the '-v' to see what files are staged/unstaged. _________________________________________________________________ Browse profiles for FREE! Meet local singles online. http://clk.atdmt.com/NMN/go/150855801/direct/01/ ``` ## Tay Ray Chuan, 2010-03-27 11:50 Subject: Re: commit --strict feature request Message-ID: URL: https://gitlist.dev/e/be6fef0d1003270450s32ab997cmfe6f6b7e6e4a16a8%40mail.gmail.com In-Reply-To: <4BA8FEA4.60504@gmail.com> ``` Hi On Wed, Mar 24, 2010 at 1:47 AM, Dario Bertini wrote: > Hi, i usually use bzr, and today i was searching for a commit --strict > equivalent in git... i asked around and it seems there isn't one, so i'm > writing this. > > basically, by doing commit --strict it refuses to commit if there are > untracked (and thus not ignored) files in the tree, this helps against > forgetting to add new files (actually i find it so useful that i've even > changed commit to be an alias to commit --strict in my bzr aliases ) check out the pre-commit hook: http://www.kernel.org/pub/software/scm/git/docs/githooks.html#_pre_commit You could make it scan the directory, then veto the execution of git-commit if any untracked files are found. -- Cheers, Ray Chuan ```