-
Notifications
You must be signed in to change notification settings - Fork 209
implement cargo_rdme readme automation for vello_hybrid
#1362
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
implement cargo_rdme readme automation for vello_hybrid
#1362
Conversation
…d-docs-automation
sparse_strips/vello_hybrid/README.md
Outdated
| cargo rdme --workspace-project=vello_hybrid --heading-base-level=0 | ||
| Full documentation at https://github.com/orium/cargo-rdme --> | ||
|
|
||
| <<<<<<< HEAD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still has conflict markers that need to be resolved...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, can't believe i missed that. I'll fix that
|
You'll also want to update |
DJMcNab
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I've pushed a few changes myself:
- I've removed the accidental reformatting of the rest of the ci.yml file.
- I've removed the double header (pre-existing issue)
- I've reduced the heading levels to match the usual expected Rust style (pre-existing issue)
- I've removed some unused links (pre-existing issue)
In general, I recommend giving any PR you open a once-over in the GitHub "Files changed" tab, to see if anything looks amiss.
The conflict markers are now gone

Resolves #1361
Using the established pattern in the workspace, this PR adds cargo-rdme markers for vello_hybrid. It ensures that the README.md is automatically synchronised with the module-level documentation in src/lib.rs
Just added cargo-rdme markers to vello_hybrid/README.md and then synchronized the files using cargo rdme --workspace-project=vello_hybrid.
You can verify by running cargo rdme --workspace-project=vello_hybrid --check. This will confirm the files are in sync without making changes.
Something to note is that the README did change. The descriptions and sections, features changed to key features and an architecture section was added.
Let me know if this is okay, thank you