-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: Document forced pushing with git #1420
Conversation
With git, there's a way to override remote trees by force pushing | ||
(`git push -f`). This should generally be seen as forbidden (since | ||
you're rewriting history on a repository other people are working | ||
against) but is allowed for simpler slip-ups such as typo's in commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*typos
@jbergstroem also perhaps worth adding "as long as nobody else has pushed to the repo in the meantime" or words to that effect. worth bringing attention to @iojs/tc, this introduces a policy of allowing force pushes for a period of 10 minutes after your push for simple fixes such as commit message typos |
@rvagg added a note about it and fixed the typo's (ha ha). |
lgtm |
(`git push -f`). This should generally be seen as forbidden (since | ||
you're rewriting history on a repository other people are working | ||
against) but is allowed for simpler slip-ups such as typos in commit | ||
messages. You are only allowed to force push to any io.js branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"However, you are only allowed"
LGTM otherwise |
LGTM too, I'm guilty of this. |
Mention that we generally disallow forced pushes but allow it in trivial cases within 10 minutes of the original push.
c22bcca
to
180190e
Compare
Updated and rebased including all suggestions. |
Thanks. It is very helpful. |
Mention that we generally disallow forced pushes but allow it in trivial cases within 10 minutes of the original push unless the branch pushed to already has new commits. PR-URL: #1420 Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
Merged in 76f219c. Thanks for the feedback and review, people. |
Mention that we generally disallow forced pushes but allow it in trivial cases within 10 minutes of the original push.
Refs #1355