4 ms·

The master tip: have a detailed written policy on git usage, on what goes into which branch, on git commit message format, and make really, really sure everyone

• Fede_V 12y ago
  Is there some kind of git plug in/linter that will check for commit style before accepting a commit? Basically, linting the commit messages.
  • candeira 12y ago
    At my current gig we use a set of git hooks, and the pre-commit hook enforces the git comment style, which performs integration with bugtracking/timetracking. We wrote our own and it's just a couple of regexes tied to a couple of warnings. Look in any git project's .git/hooks/ directory for some sample scripts.
  • eltaco 12y ago
    a pre-commit git hook? An example for jquery style commits is https://www.npmjs.com/package/commitplease https://www.npmjs.com/package/commitplease
• amelius 12y ago
  > No tips will help if the history is crap. So there should actually be a history of histories :) Perhaps something for the git team to pick up...
  • anton_gogolev 12y ago
    Changeset Evolution[1], [2] to rescue. Mercurial only, though. [1]: http://mercurial.selenic.com/wiki/ChangesetEvolution http://mercurial.selenic.com/wiki/ChangesetEvolution [2]: https://hglabhq.com/blog/2014/4/29/what-s-new-in-mercurial-3-0 https://hglabhq.com/blog/2014/4/29/what-s-new-in-mercurial-3...
• edem 12y ago
  I've seen a project where the lead guy wrote two scripts he called "git-rebase-merge" and "git-lock". Imagine when you have the ability to lock and rebase merge commits. This leads to an endless stream of errors and head scratching.