[Feature Request] Deploy a single commit to gitlab instead of multiple commits

[dheerajbhaskar]

Issue/ Current behavior

1. A lot of commits are made Problem: This pollutes your git log
2. When you have a CI setup on gitlab, a lot of builds are tried and many fail. Problem: This consumes your runner time for no good reason
3. Sometimes the most recent build fails. Problem: This gives a false positive that the site deploy failed, in fact if you just re-run the build, it just works

I hope to some day fix this myself and upstream the fix. In the mean time please let me know any details that you'd like for me to share.

Here is a screenshot of this issue:

[noone-silent]

After reading some code, i think this is managed below the "Advanced options" tab and the option "Deploy Batch Size". If you export to gitlab this should be set to Maximum (999999 files at once).

For this type I think you need a high value of set_time_limit and memory_limit.
If you are not on a shared host, maybe an option to ignore the "Deploy Batch Size" would be nice.

https://github.com/WP2Static/wp2static-addon-gitlab/blob/88fc5b785f293d787d37b3837a9717eeba7805e7/GitLab.php#L60-L66

[leonstafford]

@dheerajbhaskar the batch size won't help in this case. The previous GitHub deployer used one commit, but couldn't do diff-based deploys from WP2Static like that. I have it on the roadmap to offer different options within the GitHub deployer.

A workaround for now is to use the WP-CLI commands for WP2Static and regular git commands, deploying the exported site...