[aadrian]

Adds a "Deploy from GitBucket CI" section: a build script for gitbucket-ci-plugin that builds a static site and force-pushes it to gb-pages, using a personal access token kept in a file on the server.

Tested end to end on GitBucket 4.48.0 (CI plugin built from master) and 4.47.0 (CI plugin 1.11.0):

• first deploy creates gb-pages, later deploys replace it with a single commit
• [skip ci] keeps the push from starting a build of gb-pages
• branch builds, pull request builds, failing site builds and an empty site directory don't deploy
• the token goes through a credential helper, so it isn't in the URL or the build log
• a protected gb-pages rejects the force push (noted in the README)

The section also notes that builds run as the GitBucket OS user, so any build on the server can read the token file.

[takezoe]

gitbucket-ci-plugin is not an official plugin and personally I wouldn't broadly recommend using it because it has many known issues.