diff --git a/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment b/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment
new file mode 100644
index 0000000000..be0e490943
--- /dev/null
+++ b/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2015-09-15T17:34:15Z"
+ content="""
+What git-annex command? 
+
+`git-annex sync` should already deal with this, AFAICS. It forces the push
+to the remote's synced/git-annex branch.
+
+Some remote's may have receive.denyNonFastForwards set, which will prevent
+even a forced push. git-annex sync prints out some hints if this happens.
+"""]]