-
Notifications
You must be signed in to change notification settings - Fork 14
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
DOCSP-45284 DOCSP-45287 using the C++ driver from CMake and pkg-config #88
Conversation
✅ Deploy Preview for docs-cpp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
d20b968
to
1952195
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.
Thanks for picking this up! I left some suggestions, mostly related to the style guide (which you can read here).
Style guide-based suggestions from Nora Co-authored-by: Nora Reidy <[email protected]>
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.
oops I didn't realize I left these many comments, but let me know if you have questions about anything!
No worries. I'm working my way through them. I do appreciate all the feedback. |
Co-authored-by: Nora Reidy <[email protected]>
@norareidy in the two latest commits I have applied your suggested changes, and I also implemented the suggestion of breaking up the long sections of build output. I also created a troubleshooting sub-section. |
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 with some final comments, thanks so much for your patience with this review!
Co-authored-by: Nora Reidy <[email protected]>
@norareidy Thanks to you as well! I really appreciate all of the guidance and suggestions, as well as your patience I have learned about our documentation processes. Now that this PR is merged, should I close the associated Jira tickets? Or will you handle that? |
Of course! I can close those |
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-45284 and https://jira.mongodb.org/browse/DOCSP-45287
Staging - https://deploy-preview-88--docs-cpp.netlify.app/include-link/
Self-Review Checklist