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

This commit is contained in:
Joey Hess 2025-06-04 12:31:22 -04:00
parent 9f4e956346
commit fb9ebd12ea
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38

View file

@ -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? 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]] > [[fixed|done]] --[[Joey]]
[[!tag projects/INM7]]