-9

Does it has to do with Android Studio ? what If some one using other GUI for SVN?

Mr.India
  • 674
  • 2
  • 9
  • 19
  • 7
    Fire them if they do not "write comments/java-docs for the code before committing to SVN". – CommonsWare Feb 27 '16 at 17:22
  • 4
    I'm voting to close this question as off-topic because it is about employee management and corporate policies. – Jim Garrison Feb 27 '16 at 17:23
  • @CommonsWare I wish, I could. BTW got your point, but I was just curious if I can add some validations for commit. – Mr.India Feb 27 '16 at 17:38
  • Well, as Gavin points out, you have no good way of automatically enforcing *well-written* comments. Putting automated checks in that do not really solve the problem seems like a waste of effort. – CommonsWare Feb 27 '16 at 17:41
  • With Git you can use something like [Gerrit](https://en.wikipedia.org/wiki/Gerrit_%28software%29) to allow team members to review, approve or reject each others changes. So the team can enforce standards. – greg-449 Feb 27 '16 at 17:42
  • Thanks @greg-449, CommonsWare. But I really don't see any reasons for the down votes. – Mr.India Feb 27 '16 at 17:49
  • @greg-449 this question is a _very_ poor fit for Programmers - it would be quickly voted down and closed over there, see http://meta.programmers.stackexchange.com/questions/6483/why-was-my-question-closed-or-down-voted/6490#6490 Recommended reading: **[What goes on Programmers.SE? A guide for Stack Overflow](http://meta.programmers.stackexchange.com/q/7182/31260)** – gnat Feb 27 '16 at 19:31

2 Answers2

3

I think the problem is a little wider. While you might be able to compele somebody to add a commit message either through policy (with penalties such as formal warnings etc), or perhaps SVN has pre-commit hooks; would the messages be useful and meaningful?

Perhaps making sure you do peer reviews and education is the way to solve this issue.

Gavin
  • 1,725
  • 21
  • 34
  • @Mr.India you're welcome. – Gavin Feb 27 '16 at 18:09
  • One thing we do when committing is to include the ticket number that the work was for as the first part of the message, something like "[MyProject-42] adding validation for x y or z" – Gavin Feb 27 '16 at 18:12
  • I had an additional thought, if you are developing on branches (and you probably should be) you can refuse to merge the branch if there are commits without messages. I believe you can edit commit messages fairly easterly in SVN. Of course this requires the whole team to be of the same opinion with regard to commit messages. – Gavin Feb 28 '16 at 19:13
0

This is responsibility of team lead or project manager, when he/she assigns a project to team then a project manager/lead have to order his/her team to write comments before committing code on SVN

Mohsin AR
  • 2,998
  • 2
  • 24
  • 36