On Sunday, 25 February 2018 at 03:20:08 UTC, Seb wrote:
If you talk about using Travis to build the documentation and
push to gh-pages like e.g explained here [1]. There are
solutions:
a) Use branch protection (GH offers this. No one can force push
something to protected branches)
b) Use a dedicated bot account (if you are worried about
leaking the credentials)
c) Use a dedicated *-docs repo to which Travis pushes
d) Push to a different location (e.g. S3, netlify
...
[1]
https://forum.dlang.org/post/[email protected]
Thank! I will try to solve this