]
eyal edri [Administrator] commented on OVIRT-1001:
--------------------------------------------------
Usually the maintainer of the project does it from GitHub,
So you just need to permission updated - who should be the maintainer on the GitHub
project?
GitHub token for ovirt-engine-api-model and Travis CI
-----------------------------------------------------
Key: OVIRT-1001
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1001
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Petr Horacek
Assignee: infra
Hello,
I'd like to publish documentation made by
https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built
and deployed by Travis). I've already done that on my fork
https://github.com/phoracek/ovirt-engine-api-model but I'd like it to
be publicly available on ovirt.github.io/ovirt-engine-api-model.
What I need for that is GitHub token
(
https://github.com/settings/tokens/new) that will give me
'public_repo' scope rights (to be able to create a new branch and push
commits into it). It will be encrypted for Travis and therefore not
usable by others. Second think is to enable Travis for
ovirt-engine-api-model repository. Maybe it would be also necessary to
enable GitHub Pages on the project, but I think it will be done
automatically with branch gh-pages.
Would it be possible? Is there a better way, such as creating a new
user, give him rights for the repository and generate token for it?
Thanks,
Petr