Hi Wim, with git your commit hook is one thing, but you may need to consider a push-hook as well. When you push and things are denied you need to rebase to get your commits into a state that the push hook accepts, so thats a good thing imho but asking a lot from the programmers, especially those that are new to git. Certainly enforcing things on the proclaimed master git server (some servers are more equal than other servers, even in dscm environments) is the best way to really make sure things (code and/or commit message) come in in the expected form. With git (dscm) its just a bit more cumbersome, due to the need to rebase "broken" commits.
just my random comments... greetings, stepan -------- Original-Nachricht -------- > Datum: Tue, 8 May 2012 16:28:23 +0200 > Von: Wim Jongman <[email protected]> > An: Nebula Dev <[email protected]> > Betreff: [nebula-dev] git pre-commit hook for code format > Hi, > > I use CTRL+F constantly. This gives large code changes when I commit > something that was formatted in a different style. I use the default > jdt style btw. > > Is it possible (and desired) to run a pre commit hook that formats our > code before it hits the repo? I am looking for opinions and > experiences. > > I found this: > > http://www.blog.project13.pl/index.php/fun/1076/git-hacking-pre-commit-hook-and-custom-command/ > > Regards, > > Wim > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev -- Stepan Rutz Phone: +49 (0) 178 654 9284 Email: [email protected] Earth: Brunnenallee 25a, 50226 Frechen, Germany NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
