I especially like that they have added configuration options to the .gitlab-ci.yml. If I am not mistaken, this means your project can auto-deploy using an arbitrary build process. Here's what an example .gitlab-ci.yml looks like with a GitLab Pages build configuration: https://gitlab.com/pages/pages.gitlab.io/blob/master/.gitlab...
You can indeed have a fully automated deployment. You could already do this with GitLab CI on an external server (S3 or anything else), but now you don't have to worry about hosting anymore.
We took inspiration from .travis.yml when designing the .gitlab-ci.yml file, but are continuing to add features and configurations that make it possible to work together with other GitLab features such as build artifacts and now Pages.
One of the big limitations of Jekyll + Github pages is you cannot use plugins..any plugins at all. If Gitlab's build process allowed for Jekyll plugins and custom domains, I may consider moving my pages there as well.
You can indeed have a fully automated deployment. You could already do this with GitLab CI on an external server (S3 or anything else), but now you don't have to worry about hosting anymore.
We took inspiration from .travis.yml when designing the .gitlab-ci.yml file, but are continuing to add features and configurations that make it possible to work together with other GitLab features such as build artifacts and now Pages.