From fb9ebd12eaee1157610a37c2e5c66b7351bbc4dd Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Jun 2025 12:31:22 -0400 Subject: [PATCH] tag as INM7 because it involves git-annex integration with forgejo --- ...Pushing_current_branch_before_synced__42___or_git-annex.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/todo/Pushing_current_branch_before_synced__42___or_git-annex.mdwn b/doc/todo/Pushing_current_branch_before_synced__42___or_git-annex.mdwn index d1b7dd8e3d..e179f2e768 100644 --- a/doc/todo/Pushing_current_branch_before_synced__42___or_git-annex.mdwn +++ b/doc/todo/Pushing_current_branch_before_synced__42___or_git-annex.mdwn @@ -14,3 +14,5 @@ However, `git annex assist|sync|push` seem to push `git-annex`, `synced/git-anne Of course the solution is to just `git push` manually before `git annex assist`. But `git annex assist` is already such a brilliant command that does it all, and telling people to just run that to "do the git stuff" is very comfortable and easily accepted. Could the current branch be pushed first? Or is there a reason for pushing all the meta-branches first? > [[fixed|done]] --[[Joey]] + +[[!tag projects/INM7]]