Documentation updates and mdBook CI workflow #758
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!758
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tcpipuk/docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm still getting used to Forgejo runners, so this might involve a few commits, but I'm working on a Forgejo CI workflow for mdBook to publish to Cloudflare Pages (the domain is currently there today, but can move in the future).
Currently I'm focusing on getting the markdown files through markdownlint, and getting the workflow completing correctly, then we can start iterating updates to documentation more easily.
2d8908721de76e53a34be76e53a34b2071bdf85e2071bdf85e207ac65572207ac6557283d7f4158b83d7f4158ba8d3c395d7a8d3c395d76129e7bbfb6129e7bbfbede9a11073ede9a110735275bdb6bf5275bdb6bf20e860298120e8602981111ed6915a111ed6915a545a927c4a545a927c4a3080ab9ef43080ab9ef47f13739e847f13739e84d0e24a7971d0e24a79718cfad003408cfad003406ecd4c3ec56ecd4c3ec50ccec53d3e0ccec53d3eb1046c82c4b1046c82c4228828246c228828246c52285344d452285344d4d461bddbf26391f6610e52da66b88252da66b8828143712bb38143712bb3c2a926da41c2a926da41f758d740bcf758d740bcb15c78ae26b15c78ae26d4f742ae6fd4f742ae6fd3c40e253fSurely this should be a branch name to avoid different PRs clobbering each other?
d3c40e253fe272bd334fe272bd334fca433fbb29ca433fbb2903998437460399843746f78fd3aaa7f78fd3aaa7bbe00eafa6bbe00eafa63c7d94b5823c7d94b582094cf2d0e3094cf2d0e3697b5b05fd697b5b05fd40e47b0e6a40e47b0e6a4d9d98e03d4d9d98e03db91af70e0b