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

comment and close

Browse source
This commit is contained in:
Joey Hess 2024-02-05 14:11:47 -04:00
parent d7419d6e65
commit c0c85a7de4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/bugs/export_doesn__39__t_copy_from_adjusted_branch.mdwn
View file

@ -30,3 +30,6 @@ on Linux
### 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) ### 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. Yes, I am developing the easy-git-annex interface.
> Considering this not a bug as explained in my comment. [[done]]
> --[[Joey]]

16
doc/bugs/export_doesn__39__t_copy_from_adjusted_branch/comment_1_5ff140be453458e84bd6072594e70d8a._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2024-02-05T18:06:59Z"
content="""
You have to `git-annex sync` (or `push`) 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 origin` when 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.
"""]]