tag as INM7 because it involves git-annex integration with forgejo

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 d1b7dd8e3dc97eed569b1bef9b046025945ce059..e179f2e768ced126107cc4b7a06c433e2b09966e 100644 (file)
--- 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]]