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
Write an introduction to code reviews explaining how to make the best of a code review #4
Conversation
New content for review effectiveness including a sample agenda and sample Outlook meeting template. Updated Readme content to reflect newly added review content.
added sample agenda md link to readme fixed link to agenda oft in sample agenda
Changed from OFT to TXT file type Updated file path reference links
Added details on psychological safety, updated link order in resources
Added new content for common issues discovered during code reviews; Updated Readme content and resource links; Updated sentence structure for review agenda link.
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports You could have same capabilities but better runtime performances if you request a new MegaLinter flavor. |
updated spelling ignore list
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.
left some comments, no pressing changings
verbiage change from essential to required per Cook's suggestion. Signed-off-by: Josh Nelson <11245067+cloudappsguy@users.noreply.github.com>
2e722b5
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.
Reviewed, comments closed, ready for merge.
Description
This PR adds new content to further enhance and describe the purpose and approach to code reviews.
PR Checklist
Does this introduce a breaking change?
Any relevant logs or outputs
N/A
Other information or known dependencies
N/A