aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_1_babea9a16f25b471026732ea63dd78a8._comment
blob: 437613ee75d1799930c47b2bb6cbef5f82c589bf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2015-09-15T15:56:46Z"
 content="""
"You may need to force git to push the branch to any git repositories not
running git-annex." -- git-annex-forget man page

I guess bitbucket doesn't accept pushes that replace an existing branch
with one with a disconnected history. git push --force should sort it out.

I'm not clear how this is a bug. Is there some change needed in the 
documentation or perhaps in git-annex sync?
"""]]