From: Sri Harsha Akavaram <harsha.akavaram@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Sri Harsha Akavaramu <harsha.akavaram@gmail.com>,
git@vger.kernel.org
Subject: Re: about git hooks
Date: Tue, 20 Oct 2020 16:18:05 +0530 [thread overview]
Message-ID: <CANZ9uZyGQiRjk2Uwi0YGYRWiH4BX2SGanaJEZKW8vbmO6WM0qg@mail.gmail.com> (raw)
In-Reply-To: <20201017203822.GG490427@camp.crustytoothpaste.net>
Awesome, thanks! for your reply
On Sun, Oct 18, 2020 at 2:08 AM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> On 2020-10-17 at 14:24:10, Sri Harsha Akavaramu wrote:
> > Hi git,
>
> Hey,
>
> > I just wanted to know something about git hooks.
> >
> > we use GitHub enterprise and I'm the owner of the GitHub.
> > I'm trying to understand that I want to pose the pre-commit and
> > post-commit rules on all the developers by default and is there a way
> > to pose git hook restrictions on all developers on default.
> >
> > I came to know when reading with the documentation we cant push hooks
> > to source control. Then what is the best preferred way to pose
> > pre-commit things on all developers using the repository?
>
> This is a great question, and it's kind of answered in our FAQ[0]. The
> short answer is that you don't.
>
> It's possible for any user to simply bypass pre-commit hooks with
> --no-verify without being noticed, and there are a lot of good reasons
> to do so. For example, if I need to make a large set of changes, I may
> make a large number of temporary commits, one each time I make a change
> that works. Those commits won't meet anybody's set of standards and
> therefore won't pass the hook, and I'll need to clean them up later, but
> that helps me organize my development process in a useful way. The hook
> here would just be an annoyance that gets in the way.
>
> You may wish to provide hooks and an install script for the benefit of
> the user who wants them, but anything that runs on a developer system
> cannot be an effective control.
>
> The right way to add checks that need to apply to all users is to use
> either a pre-receive hook or a CI system, plus code review. That lets
> your tooling verify things like commit message formatting, code
> formatting, tests, and other things you'll want to check before merge.
> The code review, besides being a best practice for finding bugs and
> problems before merge, also prevents developers from neutering the CI
> system by disabling it from working properly.
>
> That's the way that most organizations handle these problems, and
> generally it works pretty well.
>
> [0] https://git-scm.com/docs/gitfaq#Documentation/gitfaq.txt-HowdoIusehookstopreventusersfrommakingcertainchanges
> --
> brian m. carlson (he/him or they/them)
> Houston, Texas, US
--
With Regards,
SriHarsha Akavaramu,
+919493841589.
prev parent reply other threads:[~2020-10-20 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 14:24 about git hooks Sri Harsha Akavaramu
2020-10-17 20:38 ` brian m. carlson
2020-10-20 10:48 ` Sri Harsha Akavaram [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANZ9uZyGQiRjk2Uwi0YGYRWiH4BX2SGanaJEZKW8vbmO6WM0qg@mail.gmail.com \
--to=harsha.akavaram@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).