News for hackers. Stuff that matters.

A comment on Git: Using Advanced Rebase Features for a Clean Repository. Parent comment

Re:Git: Using Advanced Rebase Features for a Clean Repository by lolive on Wednesday August 09, 2017 @12:55PM (#14971150)
How do you enforce a commit policy in your projects?

Do you automate it?

Or do you provide feedback by mail, IM, ... to the author when a commit mistake is detected?

[ Parent | on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository by lomnakkus on Wednesday August 09, 2017 @06:11PM (#14974206)
Review-before-merge, maybe?

Obviously, for any old arbitrary project, there's going to be limits to what you can ask your contributors to conform to before they just leave, but we're discussing "Best Practices"[1] here.

I think these articles are useful because they spread the knowledge of "How To Be A Good Contributor"... for free.

[1] Ugh. Not a term I like, but really this is almost always(!) the best way to do it.

[ Parent | on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository by nicwolff on Wednesday August 09, 2017 @04:01PM (#14973031)
We have a GitHub integration that runs on every pull request and push, which triggers an AWS Lambda function that verifies that disables the big green "Merge" button if the branch could not also be fast-forwarded onto its parent.
[ Parent | on HN ]