comment and close

diff --git a/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch.mdwn b/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch.mdwn
index 91b45aef8fe721d0b17653d81690e9d1c4ac148d..7cf57892e894d06f3c95f07bc1f4abb561e4e972 100644 (file)
--- a/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch.mdwn
+++ b/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch.mdwn
@@ -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)
 
 Yes, I am developing the easy-git-annex interface.
+
+> Considering this not a bug as explained in my comment. [[done]]
+> --[[Joey]]

diff --git a/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch/comment_1_5ff140be453458e84bd6072594e70d8a._comment b/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch/comment_1_5ff140be453458e84bd6072594e70d8a._comment
new file mode 100644 (file)
index 0000000..cee7fdf
--- /dev/null
+++ b/doc/bugs/export_doesn__39__t_copy_from_adjusted_branch/comment_1_5ff140be453458e84bd6072594e70d8a._comment
@@ -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.
+"""]]