-
Notifications
You must be signed in to change notification settings - Fork 108
✨ Add workflow for a book publishing job #331
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
✨ Add workflow for a book publishing job #331
Conversation
33ab8d5
to
58d8160
Compare
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexander-demicev The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
/lgtm
awesome work! thanks Danil
LGTM label has been added. Git tree hash: 2a02977e10a7ac9ca62df4b87f49efd0e0cd7ec1
|
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 @Danil-Grigorev for the PR!
@@ -0,0 +1,8 @@ | |||
# Cluster API Operator |
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.
file name could be just introduction.md
without numbering, but should be fine as a initial base for the book
/lgtm
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.
This structure is using https://lib.rs/crates/mdbook-fs-summary - it might be easier to handle summary generation then doing this manually, and less chances that it will leave broken links. That's why it has 01_ in the front
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #330