BaseLine Update WorkFlow config

[c9mb]

We have multiple sites based on a baseline master, and plan to deploy many more sites this way.

The baseline master provides us with the initial default deployment of a site, and the child site is then customised to meet the client's specific requirements.

As the baseline is updated with code changes from both internal development and Umbraco upgrades, these are deployed to the child sites, and for the most part this works ok.

However, for some files, updating the baseline master to improve and/or enhance future default deployments, results in existing child site customisations being nuked, and additional work required to recover those customisations. Examples of such files might be css, js, fonts, images, etc.

You can't control this action using gitignore, as that would break the ability to update projects from local development, and so controlling this requires the ability to override the baseline update deployment workflow.

I would like to be able to specify such files in a .config, that the baseline update workflow examined as it deployed changes to existing child sites, so that changes to these files could be ignored as required.

UmbracoBaseline.config <childupdates> <ignore> <add path="/pathmatch/filematch*.css" /> <add path="/pathmatch/filematch*.js" /> </ignore> </childupdates>

The baseline update workflow could then read that .config file and process child updates using that as a control.

Being a .config could also offer the Umbraco devs team a tool to extend other control features people might want to introduce into the baseline workflow in the future.

Also, being a .config opens the door to transformations for environment-specific workflows, although I don't have any specific applications in mind for that at the moment.