You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are not a fan of giving a GITHUB_TOKEN, which I totally agree (it is like giving our GitHub password), then an other option is to add a SSH public key to the repository.
The issue is that your account will be now the committer.
I have made an image, but the script can be used directly: https://github.com/j8r/dockerfiles/tree/master/gh-pages-ci.
A third option can also be to create a new GitHub user for this.
@veelenga If it is possible to use GitHub Actions, I can do the docs automation myself (I have already done this for some other of my projects) - and no token needed.
The CI can generates docs, then pushing them to the
gh-pages
branch.Travis CI docs: https://docs.travis-ci.com/user/deployment/pages/
If you are not a fan of giving a
GITHUB_TOKEN
, which I totally agree (it is like giving our GitHub password), then an other option is to add a SSH public key to the repository.The issue is that your account will be now the committer.
I have made an image, but the script can be used directly: https://github.com/j8r/dockerfiles/tree/master/gh-pages-ci.
A third option can also be to create a new GitHub user for this.
cc @veelenga
The text was updated successfully, but these errors were encountered: