Re: [Edgex-tsc-devops] Gofmt git commit hook
Dell - Internal Use - Confidential
Thanks, Jeremy. It looks like the git-hooks utility you linked to below would allow us to create a git-hooks directory in our repo and then put the appropriate scripts in there. This would allow us to source control the scripts.
It also looks like their “community hooks” would allow us to create a repo specifically for githook scripts. Then all we’d have to include in our projects is a githooks.json file like this one. Execution requires internet connectivity though, obviously.
We’d need to require all developers to install the utility if we go down this route.
From: EdgeX-TSC-DevOps@... [mailto:EdgeX-TSC-DevOps@...] On Behalf Of Jeremy Phelps
Sent: Friday, June 15, 2018 1:10 PM
To: Conn, Trevor
Cc: EdgeX-TSC-DevOps@...; EdgeX-GoLang@...
Subject: Re: [Edgex-tsc-devops] Gofmt git commit hook
I am in favor of something like this generally. I think because we use GitHub we will have to have client side hooks ( I will look into it further though ). There are tools available to help share commit hook scripts such as https://github.com/git-hooks/git-hooks/wiki/Get-Started. Lets put this on the table for discussion, we can ramp up the DevOps WG meetings again if we need extra time.
On Fri, Jun 15, 2018 at 12:12 PM, <Trevor.Conn@...> wrote: