4

I've been looking for this for quite a while myself, but I have nearly no experience with the subject, so I'm just hoping that someone here has come across this before.

Would it be possible to run some kind of a script in SourceTree, which would check the files for some criteria (for example, going through the files checking if "StaticMethodX." is used anywhere and failing the commit attempt if it is?

I'm trying to enforce better coding standards within a team.

Any help is highly appreciated.

BJ Myers
  • 6,617
  • 6
  • 34
  • 50
EvilBeer
  • 2,054
  • 2
  • 19
  • 37

2 Answers2

6

You can either:

  • ask your client to use a pre-commit hook (also presented in this article or illustrated in this question), but they can bypass it if they want

  • or you can set up a pre-receive hook which will deny the push on the server side if your policy isn't followed.
    It would use git diff-index --cached --name-only, as in this question to get the content of each file pushed.

The server-side approach is generally favored, as it is easier to deply, maintain and enforce.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • "The server-side approach is generally favored, as it is easier to deply, maintain and enforce." => but a client side is nice in complement to avoid having to wait until the push to know your commits are broken and unpushable. – Matthieu Moy May 04 '15 at 06:36
  • @MatthieuMoy I agree. It is just harder to deploy, enforce and update. – VonC May 04 '15 at 06:36
  • @VonC: yes, I was not disagreeing ;-). Just complementing your answer. – Matthieu Moy May 04 '15 at 11:46
0

Try npm pre-git which allows you to run commmands on pre-commit and pre-push. Than open sourcetree using Terminal with following command

open /Applications/SourceTree.app/Contents/MacOS/SourceTree

Now you try to commit and push, sourcetree will run pre-commit and pre-push hooks.

Aamir Afridi
  • 6,364
  • 3
  • 42
  • 42