From e001f275aead09eba6b96d7440200e166667e273 Mon Sep 17 00:00:00 2001 From: Chris O'Connor Date: Tue, 19 Aug 2014 14:48:43 -0400 Subject: [PATCH] avoid force pushing --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index dab1a10..833e6e4 100644 --- a/README.md +++ b/README.md @@ -29,6 +29,8 @@ For clarity's sake all examples in this document use customized bash prompt in o Note that, as with rebasing (see below), amending **replaces the old commit with a new one**, so you must force push (`-f`) your changes if you have already pushed the pre-amended commit to your remote. Be careful when you do this – *always* make sure you specify a branch! +In fact, if you are not the only developer using the repo **avoid force pushing**. It is best to create and push a new commit rather than force-pushing the amended commit as it has the potential to mess with the shared history. + ## I need to combine commits