I am trying to gain some traction on a new SPO project and it's been indicated to me that they want to maintain the site programmatically with PnP templates (XML files basically). The idea is that we have a git repo with our PnP templates with the aim that we could hook it up to continuous integration and as we update the template it deploys directly from source control.
However I am not sure if this is the correct approach at all. Barring trial and error I don't feel confident that I can determine if a PnP template XML file being changed and deployed repeatedly to the same tenant will gracefully deploy changes in the first place.
In fact, I don't even know if this is the best workflow at all, but it's been indicated to me that editing the XML is the development process... something doesn't smell right about it though.
Note that I am coming from a traditional full-stack development background where I am most familiar with the workflows of rolling ASP.NET websites with JS front-ends and EF/SQL in the back. Through that lens this SharePoint development/versioning/deployment stuff is rather disorienting.