forum/Issues with non-sync workflowgit-annexhttp://git-annex.branchable.com/forum/Issues_with_non-sync_workflow/git-annexikiwiki2022-05-09T19:18:01Zcomment 1http://git-annex.branchable.com/forum/Issues_with_non-sync_workflow/comment_1_99f89201446005f77d9278a7a889638d/joey2022-04-19T18:05:09Z2022-04-19T16:28:06Z
<p>I don't think anything git-annex can do would make git worktree behave the
way you want it to behave, except for a whole separate mode of operation
that writes to the git-annex branch via writing to the worktree for it and
committing.</p>
comment 2http://git-annex.branchable.com/forum/Issues_with_non-sync_workflow/comment_2_f27ec2462e5a8f6f96c6e2b7dd3f87ca/lh2022-04-19T18:15:53Z2022-04-19T18:15:53Z
<p>But the worktree won't confuse git-annex in any way, right?</p>
<p>If that's the case, I guess I'll just remember to hard reset the worktree every time I want to work with it. As long as git-annex doesn't ever leave things uncommitted on its branch, that should be fine.</p>
comment 3http://git-annex.branchable.com/forum/Issues_with_non-sync_workflow/comment_3_db02b002a977b57be0102d8ac7c2037f/lh2022-04-19T18:40:57Z2022-04-19T18:40:57Z
If I had set annex.alwayscommit=false, would that make resetting the worktree potentially dangerous if I hadn't merged yet?
comment 4http://git-annex.branchable.com/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d/lh2022-05-09T19:18:01Z2022-05-09T19:18:01Z
Still curious about how <code>annex.alwayscommit=false</code> tracks modifications and whether mucking with a <code>git-annex</code> worktree could cause data loss with this option enabled.