Well, I'd still go with automated tests, as a colleague suggested. I believe it is very dangerous to prevent commits. As long as it is a personal branch, one should go for it and do whatever they want.
Checklists? I'd surely add them to merge/pull requests.
As a midway point, I would run my checks while detaching from the terminal and returning a 0 exit code. That way, I would still have my checks while creating my commits and keeping changes safe in their place.
Something like:
#!/bin/bashfunction main(){sleep 10
echo'Do my stuff'}
main &
exit 0
Maybe some voice messages to give alerts etc, e.g., say when using OS X.
Before I forget and you think I came here to say it is a bad post: I totally loved it! :) It is very important to educate people on hooks
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, I'd still go with automated tests, as a colleague suggested. I believe it is very dangerous to prevent commits. As long as it is a personal branch, one should go for it and do whatever they want.
Checklists? I'd surely add them to merge/pull requests.
As a midway point, I would run my checks while detaching from the terminal and returning a 0 exit code. That way, I would still have my checks while creating my commits and keeping changes safe in their place.
Something like:
Maybe some voice messages to give alerts etc, e.g.,
saywhen using OS X.Before I forget and you think I came here to say it is a bad post: I totally loved it! :) It is very important to educate people on hooks