4 ms·
Yes, just a kid crying about having to follow style guidelines. If manually running his team's tool is really wasting as much time as he claims, they should swi
by slacka 9y ago
Yes, just a kid crying about having to follow style guidelines. If manually running his team's tool is really wasting as much time as he claims, they should switch to a tooling that automatically corrects style. I use tabs, but the policy is spaces. When I commit a change, my my tabs are automatically controverted to spaces. Zero time lost and no one fights about tabs vs spaces.
- nulagrithom 9y agoJust a thought -- it would be neat to see a project that would allow you to check the code out again with your tabs instead of the committed spaces. More of a style translator than an enforcer.
- xaedes 9y agoIt should be relatively easy to set up with git hooks: Take one of the many Git Hooked Autoformaters: For example: https://github.com/michalrus/git-hooks-code-autoformat https://github.com/michalrus/git-hooks-code-autoformat Then add similar hooks for pulling on "post-merge" and "post-rewrite". There is no hook for "pull" per se, but either a merge or commit rewrite (rebase) happens after pull that changes code. So you should be good with those both hooks
- dang 9y ago> Yes, just a kid crying about This breaks the HN guidelines against calling names in arguments, so please don't do that. Your comment would be just fine without the first sentence.
- gvb 9y ago"tabs are automatically controverted to spaces" I don't know if that was a typo or intentional, but I like it!