From f8fe393052be1fb24bb7487a4ef43f8677b10fa1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 17 Oct 2022 12:37:57 -0400 Subject: [PATCH] comment --- ...ment_1_f83dbcfdd09de3ce908c0d4a9daef458._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/Failed_to_push_on_git-lfs/comment_1_f83dbcfdd09de3ce908c0d4a9daef458._comment diff --git a/doc/forum/Failed_to_push_on_git-lfs/comment_1_f83dbcfdd09de3ce908c0d4a9daef458._comment b/doc/forum/Failed_to_push_on_git-lfs/comment_1_f83dbcfdd09de3ce908c0d4a9daef458._comment new file mode 100644 index 0000000000..f3c9d06728 --- /dev/null +++ b/doc/forum/Failed_to_push_on_git-lfs/comment_1_f83dbcfdd09de3ce908c0d4a9daef458._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-10-17T16:28:48Z" + content=""" +This doesn't involve LFS at all, it's a regular git branch being pushed in +the regular way. So you can certianly solve the problem with some +combination of `git pull`, `git merge`, and `git push`. + +That said, I don't know why `git-annex sync` didn't work in your situation. +I created some test git-lfs repos on github and never saw any difficulty +syncing with them. +"""]] -- 2.30.2