diff options
| author | bors <bors@rust-lang.org> | 2023-06-17 03:28:53 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-06-17 03:28:53 +0000 |
| commit | 1d7d82472617a4a0fea59c7e239c8a48c8ac5c34 (patch) | |
| tree | ea7bd8fbd577e66f64a46f88ca6272494982cf98 /compiler/rustc_codegen_cranelift/example/alloc_example.rs | |
| parent | 0cc541e4b2eb957e71490cf44df1ac09f6d18132 (diff) | |
| parent | 696b0dd472d42c7e71c992bd2e3def2d40fadebb (diff) | |
| download | rust-1d7d82472617a4a0fea59c7e239c8a48c8ac5c34.tar.gz rust-1d7d82472617a4a0fea59c7e239c8a48c8ac5c34.zip | |
Auto merge of #112407 - tgross35:ci-docs-publish, r=Mark-Simulacrum
Publish docs as github artifacts during CI Discussed here: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI The goal is to make docs available for download after CI runs on PRs, for easy review of API changes. Notes: - Currently this only captures library documentation (`core`, `alloc`, `std`, `test`, `proc_macro`) - You can't see artifacts until the entire workflow run has completed https://github.com/actions/upload-artifact/issues/53 - There is currently a generic file name `ci-artifacts`. No way to customize this based on contained files unfortunately https://github.com/actions/upload-artifact/issues/349 You can find the results at the bottom of the CI "summary" page: <img width="379" alt="image" src="https://github.com/rust-lang/rust/assets/13724985/d3748e59-242c-40f8-9f54-82177b9b481b">
Diffstat (limited to 'compiler/rustc_codegen_cranelift/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions