#20953: git push -f in docs needs a stern warning
--------------------------------------+------------------------------------
Reporter: EvilDMP | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by EvilDMP):
People who ''do'' want to push ''should'' use SSH. This is for people who
''don't'' want to find themselves pushing inadvertently, as I did last
week.
It's true that there will be a very small number of people who find
themselves in my position - with write access, and just enough knowledge
to be dangerous - but even one is quite enough.
I've been through a certain amount of discussion on #git and #github, and
even conversations with GitHub support about the deprecated 'git://'
format, and using HTTPS rather than SSH does seem to be regarded as an
acceptable way of putting up a barrier for oneself to accidental pushing.
But if that's not a good solution, and the documentation should no longer
say to use `push -f` after squashing, what ''should`` it say?
--
Ticket URL: <https://code.djangoproject.com/ticket/20953#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.71dc41ac7e95636f78646c2211dba3ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
