-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Documenting ways for in-file and cross-file navigation #32154
Documenting ways for in-file and cross-file navigation #32154
Conversation
@MichalMaler - reviewing now. Thanks |
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 suggested a few changes (once).
I don't understand why we duplicate this content so many times? It will be a nightmare to maintain.
The task was to add this to contributor and other related docs, and since many dont read the contributor docs while at least using templates to create a new file, I add this info to our templates too (so there is a chance that before removing of the content from the template they will read it). @gsmet Thank you for the review |
77dacd4
to
2bb430f
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.
@MichalMaler - Nice job 👍
Please see my suggestion for how you could avoid duplicating the same content in several places. Thanks.
@michelle-purcell Thank you for the review and suggestions, Michelle. Lets make it work! |
2c3fa26
to
a3bc5ff
Compare
@michelle-purcell @gsmet Applied all your suggestions in my own way :) Content is now added to Upstream docs in these two places and forms:
2)doc-reference.adoc#cross-references
Templates now only contain xrefs where a contributor can get the information if needed thus nut duplicating the content. |
a47f2bf
to
ee473be
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.
@MichalMaler - Super job! Looks great. Thank you 💚
🙈 The PR is closed and the preview is expired. |
ee473be
to
118263a
Compare
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
87a0245
to
236bc41
Compare
@ebullient Thank you Erin. Added your suggestions. This can be merged at will now. |
@gsmet Can we merge this if you agree? |
32870dd
to
4f7c5fa
Compare
crap. I messed that up. will try to fix |
33139ed
to
c400e43
Compare
@ebullient Did not spot anything broken. |
c400e43
to
36605f3
Compare
Signed-off-by: Michal Maléř <[email protected]> Docummenting ways for in-file and cross-file navigation Signed-off-by: Michal Maléř <[email protected]> Review Signed-off-by: Michal Maléř <[email protected]> Review and fixes Signed-off-by: Michal Maléř <[email protected]> Review and fixes Signed-off-by: Michal Maléř <[email protected]> Review and fixes Signed-off-by: Michal Maléř <[email protected]> Review and fixes Signed-off-by: Michal Maléř <[email protected]> Review and fixes Signed-off-by: Michal Maléř <[email protected]> Apply suggestions from code review Co-authored-by: Erin Schnabel <[email protected]> Apply suggestions from code review Co-authored-by: Erin Schnabel <[email protected]>
e7b601d
to
0a428ea
Compare
@maxandersen Hello Max. This PR was approved by other writers and Erin. Please, what needs to be done so that we can merge this? |
Thank you for the approval @jmartisk |
After the xref and anchors clean-up and unification, I follow-up on @gsmet work and adding the steps for proper ID creations ant their calls.
Adding full specification to our contributors doc and light-weigh version for our templates.
Closing: https://issues.redhat.com/browse/QDOCS-267
Reference: #31981
Will squash n rebase after a review.