mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

relax annex-tracking-branch to allow "/"

Browse source 
Allow setting remote.foo.annex-tracking-branch to a branch name that
contains "/", as long as it's not a remote tracking branch.
This commit is contained in:
Joey Hess 2025-01-20 11:31:18 -04:00
parent b1c9c9d6e7
commit 9e4314de76
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 34 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/Can__39__t_export_synced__47___branches.mdwn
View file

@ -66,3 +66,5 @@ export myexport bla ok
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
git-annex is amazing, thank you! 🤩
> [[fixed|done]] --[[Joey]]

19
doc/bugs/Can__39__t_export_synced__47___branches/comment_1_19ef18864eef6d08dae48df6ddb7152d._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2025-01-20T15:13:05Z"
content="""
The difficulty here is that it needs to come up with the name of a
corresponding remote tracking branch to update. It could use
"myexport/synced/main" for that. But, setting `annex-tracking-branch` to
a remote ref like "origin/main" is not supported, and it would not be good
if it allowed it and used a tracking branch with a name like
"myexport/origin/main".
And well, we know that "synced/main" is not a remote ref, but "$foo/main"
generally may or may not be one.
So, I think to support this, it would have only allow using "$foo/main"
when the ref "refs/remotes/$foo/main" does not exist. I've implemented
that.
"""]]