tag as INM7 because it involves git-annex integration with forgejo
This commit is contained in:
parent
9f4e956346
commit
fb9ebd12ea
1 changed files with 2 additions and 0 deletions
|
@ -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]]
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue