I'm wondered if anybody had any advice on best practices for source control and uSync. I'm currently only including the 'uSync' folder and ignoring the archive folder.
I believe I've set my GitAttributes correctly, but I'm finding that Git is picking up 'changes' in the .def files, which are in-fact just whitespace differences. Has anyone else experienced this?
Yes i have seen that, it's actually the reload process inside umbraco - if you change the stylesheet on disk and then reloads the stylesheet tree in umbraco it appears to append an extra line onto the end of the stylesheet.
usync is just reflecting that change to the stylesheet (i think) - I turned off stylesheet syncing in frustration only to see it continue to happen inside the CSS folder :(
uSync, Source Control, Best Practices for Whitespace
Good morning (guten Morgen),
I'm wondered if anybody had any advice on best practices for source control and uSync. I'm currently only including the 'uSync' folder and ignoring the archive folder.
https://github.com/uniquelau/vdb.Common.Project/blob/master/VS.NET/company.project.Web/.gitignore
I believe I've set my GitAttributes correctly, but I'm finding that Git is picking up 'changes' in the .def files, which are in-fact just whitespace differences. Has anyone else experienced this?
My solution was the update the .gitconfig with:
Source Stackoverflow Post
Yes ignoring the archive is the best bet
I haven't noticed the white space issue, but if the .gitconfig updates fix it i might start using that.
Spoke to soon! ;) It's still an issue. Doh!
Yes i have seen that, it's actually the reload process inside umbraco - if you change the stylesheet on disk and then reloads the stylesheet tree in umbraco it appears to append an extra line onto the end of the stylesheet.
usync is just reflecting that change to the stylesheet (i think) - I turned off stylesheet syncing in frustration only to see it continue to happen inside the CSS folder :(
Yep, it's a bit of a pain! Esp if you've lots of stylesheets! >.<
I couldn't find an issue for this, so I've created a new one:
http://issues.umbraco.org/issue/U4-3033
is working on a reply...