-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Fix LightningCLI docs after overhaul of the documentation #14976
Fix LightningCLI docs after overhaul of the documentation #14976
Conversation
- Change the docs to be focused on configure hyperparameters instead of reduction of bolierplate.
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.
Great improvements!
One suggestion for future work: In large PRs like this one, it would be great if you could give the reviewer some guidance on what has been moved where, as it is not so easy to discover just from the diff.
Co-authored-by: Adrian Wälchli <[email protected]>
- Change the docs to be focused on configure hyperparameters instead of reduction of bolierplate.
@RobertLaurella could you pls check this out 🦦 |
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.
great work!
is there a book on lightning cli? 😄
Head branch was pushed to by a user without write access
Question. Why is this v1.9? It only fixes the documentation of what is currently supported. Nothing related to new features. |
@mauvilsa We don't usually cherry pick docs updates into our bugfix releases (1.8.x), which is why this is labelled 1.9. Once this is merged, the changes will appear on the website under "latest". I think we should move forward and merge this as soon as possible :) Note: Might also be worth checking #15473 for possible collisions as it will probably land very soon too. |
What does this PR do?
Fixes #13249
I found many more issues not mentioned in #13249. And still some things might need improvement, hopefully we can fix them with the reviews.
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃
cc @carmocca