diff options
author | Lucas Nicodemus <shank@shanked.me> | 2018-10-04 08:08:31 -0700 |
---|---|---|
committer | Lucas Nicodemus <shank@shanked.me> | 2018-10-04 08:08:31 -0700 |
commit | cbafd5d225dc0fe4877cdcb92c032d5034558df9 (patch) | |
tree | 6d3177ac7ba04d8cb585c3a264ba9387d00355c3 /guides/source/working_with_javascript_in_rails.md | |
parent | 414c70e072466ebe40e7c46795f27c48cba8d717 (diff) | |
download | rails-cbafd5d225dc0fe4877cdcb92c032d5034558df9.tar.gz rails-cbafd5d225dc0fe4877cdcb92c032d5034558df9.tar.bz2 rails-cbafd5d225dc0fe4877cdcb92c032d5034558df9.zip |
Change contributing guide to use safer force push
This commit changes the contributing guide in rails to suggest using git
with force-with-lease over typical force pushing. In practice, most
rails contributors won't ever encounter a situation where updating their
local fork could result in lost changes as a result of a force push.
That being said, git is a complex tool and arcane flags like
force-with-lease are indeed safer, and by promoting it in rails, there's
a chance more people will discover it and use it in other contexts
outside of rails. In just the same way that herd immunity works by most
people being vaccinated, proliferating knowledge of force-with-lease
should help nudge people towards using safer git commands in general.
[ci skip]
Diffstat (limited to 'guides/source/working_with_javascript_in_rails.md')
0 files changed, 0 insertions, 0 deletions