-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for incremental deployment #991
Labels
General Enhancement
New feature or request
Comments
Highly desirable feature indeed! |
i agree @atiq-cs, perhaps this also affects the current issue where building with github pages that build from a specific branch will wipe out the existing CNAME file [when using a custom domain, specific to branch based pages deployment]. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is an unserved use case where only parts of the generation are run and the resulting output files only represent a subset of all files that constitute a full site. When running in this mode we need a way to deploy only those changed files without deleting everything else that's already been deployed.
Right now the built-in deployment modules generally upload and deploy everything in a "full merge" mode. In GitHub this means uploading every output document as a blob and creating a full commit tree. In Azure and Netlify this means uploading a zip file with the full output. Ideally we'd have a setting for every deployment environment that toggles from a "full merge" mode to a "overwrite changes" mode - though that's highly dependent on what the various environments support.
cc @Simply007
The text was updated successfully, but these errors were encountered: