I think I'd somewhat misunderstood how git backed deployments work...
I'd thought the git deployments would only trigger when the manifest.json files were updated - but it seems like the git deployments happen when any changes happen on the branch. Also I thought the manifest would be checked for a list of files and their hash codes... but actually these to be ignored?
How I found this... If I look inside an app folder like /var/lib/rstudio-connect/apps/7/29/ then it seems like the deployed app contains more files than just the files mentioned in the manifest - e.g. if I add files inside an R folder than those files trigger a deployment and get deployed.
Is there any more info available about how git backed deployments work beyond the docs on
I'm especially wondering about whether I can exploit this behaviour to make some deployments simpler for our less technical developers - can I rely on the fact that the hash codes and file lists in manifest.json don't matter for the git backed case? Can I rely (for a major version at least) on all folder files to be deployed alongside each app?
From an admin perspective I guess I'm also a bit surprised that if the manifest and files get out of sync, then I don't even get a warning alert about this - the deployments seem to just succeed regardless?