Add a job to build and deploy the main branch doc on Github pages #461
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As proposed in #460, I suggest to host the doc of the git version of rclrs on Github pages.
In order for it to work, you need to enable Github Pages on this repo:

I understand @esteve point in #460 (comment) that people using the git version of rclrs can do
cargo doc
themselves because the doc is already published on doc.rs for the released version of the crate so feel free to decline my PR if you prefer.But I my point was to ease the access to the documentation of the git version instead of adding simple examples that have the same content than the rustdoc snippets to reduce the maintenance effort on API changes.
The workflow was tested on my fork in the feature/add_doc_job with the result exposed here. I had to do a different branch for the PR to point to the
main
branch of this repo.