Please describe the problem.
Exporting to a directory remote with exporttree=yes works if the source repository is not on an adjusted branch.
If, before the export, git annex adjust is invoked with --unlock or --lock (the only two I tested) the new files are not copied.
FWIW, annex.adjustedbranchrefresh is set true.
What steps will reproduce the problem?
git annex export --json-progress --to export-special-remote main:Music
What version of git-annex are you using? On what operating system?
10.20231228-g5540f42e21afce6947d5410c5f18b178de6c336a
on Linux
Please provide any additional information below.
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
# End of transcript or log.
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)
Yes, I am developing the easy-git-annex interface.
Considering this not a bug as explained in my comment. done --Joey
You have to
git-annex sync(orpush) first to get your changes propagated from the adjusted branch to the main branch that you are exporting.(You could alternatively export the adjusted branch itself.)
This is the same as if you tried
git push main originwhen on an adjusted branch. It would surely not be a bug that doesn't push changes you have only committed to the adjusted branch. So I think it's reasonable for the export workflow to need the same step that the git push workflow needs.