Building websites on TravisCI
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
In addition to the instructions at ?pkgdown::deploy_site_github, you need to ensure you can install apps on GitHub. For that, you need owner privilege to the repo you want to setup. Then travis::use_travis_deploy() should be able to install the required apps, and they should be able to build the website, even if other apps are restricted.
The package is linked to the “rtravis” application, and will request GitHub permissions to carry out its actions. We try hard to minimize the scope of the permissions we request, but this may lead to multiple authentication requests. Revoking these permissions also invalidates any SSH keys created by this package.
-- https://ropenscilabs.github.io/travis/
This is what things should eventually look like:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced ?pkgdown::deploy_site_github instructions and the ropenscilabs.github.io/travis guide; review the rtravis deployment flow and linked screenshot. Done when the documentation clearly explains repository ownership, app installation, permissions, and the expected website build result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, r
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100