Repository navigation
git-filesync 0.23.3
Try a newer version in the working tree; staged changes count as uncommitted
Changes:
- pull -W/--worktree: write what pull would sync into the working tree
only - nothing staged, .git-filesync unchanged - e.g. to see whether
your project still builds with it. 'git restore' goes back,
'pull --overwrite' takes it. - pull --overwrite also discards uncommitted changes, keeping them
('discarded: ... (git show ...)'); nothing is reported as discarded when
the file already has what is written. - Staged changes are uncommitted changes: status reports them (also with
the working file as in HEAD again), and pull and rm refuse them like
changes in the working tree. - Commands that stage .git-filesync warn if it had changes not staged
before; those are staged too. - Hints say 'git restore -SW' to discard uncommitted changes.
Compatibility:
- pull --overwrite (also with --all) no longer refuses uncommitted
changes: it discards them, keeping their content as a Git object. - rm without -f refuses files with staged changes.
Documentation:
- MANUAL: "Trying a newer version".