-
Notifications
You must be signed in to change notification settings - Fork 687
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
Tweniee/Isssue:#11361 Updated Document for PR release #11512
Conversation
Build Artifacts
|
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.
Hi @Tweniee, thank you for your contribution! I've left a few notes.
Also, I don't see the new page on the documentation preview https://kolibri-dev--11512.org.readthedocs.build/en/11512/ (this link is available in the checks section of this pull request). It needs to show in the menu as well as in the list of the "How To Guides" page:
Were you able to run the documentation locally and preview it?
@MisRob made the required changes and improved few statance according to your changes please do review it and thanks for your time and suggestions |
Thanks @Tweniee, I will re-review |
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 for your cooperation @Tweniee, it's much better. Not completely there yet though, I left a few notes. Let me know if you had any questions.
|
||
Locally, checkout your feature branch (that you previously created off the develop): | ||
``` | ||
git checkout develop |
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.
A feature branch is not the develop
branch, so please remove this line, it's not a step that people should do. I've tried to explain this a bit in the previous review, you're welcome to ask any clarifying questions if it's not clear.
@@ -0,0 +1,32 @@ | |||
# Rebasing a Pull Request |
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.
I believe the primary title will be shown on the generated page as the result of being automatically propagated from the corresponding .rst
file so this would cause it to appear two times. Therefore, let's remove it.
I guess this will do the work @MisRob |
Thanks for following-up, @Tweniee. I can see two remaining feedback items that still need to be resolved. |
@MisRob Sorry for that, i missed it. now i guess it look fine. |
Thanks @Tweniee. I will re-review some time next week. |
Sure @MisRob 😃 |
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.
It's looking good @Tweniee! Thank you for all work. One last thing before we can merge - the linting check is failing. Could you run pre-commit as described in this section of the developer documentation?
@MisRob linting is done just one |
@Tweniee Thank you! No the other check is okay, it's a problem on our side. I will deal with it. |
Summary
Incorporated rebase functionality into the documentation
Previous PR:#11509
References
Issue:#11361
Reviewer guidance
Its a documentation change onl
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)