-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Host documentation #5
Comments
Also related to this: https://github.com/onur/docs.rs/issues/93 |
I know this is a really old issue, but I found a way to do it with GitHub's new Actions to Pages functionality. Below is an example, and you can find working documentation hosted on my fork, that was built with GitHub actions. name: Rust
on:
push:
branches: [ "master" ]
pull_request:
branches: [ "master" ]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: true
env:
CARGO_TERM_COLOR: always
jobs:
build:
runs-on: macos-latest
steps:
- uses: actions/checkout@v3
- name: Document
run: cargo doc --verbose
- name: Packaging
run: mv target/doc _site
- name: Upload artifact
uses: actions/upload-pages-artifact@v1
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v1 You (@kvark) have to set it up in the repository settings though. |
Since this is no longer true, should this issue be closed? |
If this still true? The about builds page for docs.rs says:
Correct me if I'm wrong, but wouldn't out-of-ecosystem platform specific libraries still be needed, that couldn't be brought in? |
@IsaccBarker would you mind making a PR? |
I'm able to generate documentation for |
I think this can be closed now that #303 landed |
Most of the project rely on
docs.rs
for documentation, however it only builds Linux at the moment. We need to find a good way of providing the documentation here.cc @fkaa @JohnColanduoni
The text was updated successfully, but these errors were encountered: