You'll notice
Useful3 Signal1
One awkward .gitignore line no longer makes sync reject the whole file.
What's wrong with this entry?
Anonymous. No account, no email.
What
Ignore lines that sync previously could not match are now rewritten where possible rather than rejected, so a single tricky line no longer makes the whole .gitignore count as too complex to use.
Details
- Trailing blanks and unicode spaces, bracket expressions, escapes and case-folding differences are normalized.
- Rewritten lines are reported as
adjustedwith a reason of either "wildcards" or "spelling", and are marked internally as having been widened, so sync knows where it now matches more than git would. - Applies to directory sync only.
Evidence
a bracket expression, an escape or a trailing blank that sync reads differently from git
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory