Skip to content
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

cloudappsguy
Copy link

@cloudappsguy cloudappsguy commented Nov 17, 2023

Description

This PR adds new content to further enhance and describe the purpose and approach to code reviews.

PR Checklist


Use the check-list below to ensure your branch is ready for PR. If the item is not applicable, leave it blank.

  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My code follows the code style of this project.
  • I ran the lint checks which produced no new errors nor warnings for my changes.
  • I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does this introduce a breaking change?


  • Yes
  • No

Any relevant logs or outputs

N/A

Other information or known dependencies

N/A

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.
Copy link

github-actions bot commented Nov 17, 2023

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.02s
✅ MARKDOWN markdownlint 247 0 5.91s
✅ MARKDOWN markdown-table-formatter 247 0 0.57s
✅ MDLINKCHECK linkcheck 247 0 11.4s
✅ SPELL cspell 258 0 11.84s
✅ YAML prettier 10 0 1.45s
✅ YAML yamllint 10 0 0.52s

See detailed report in MegaLinter reports

You could have same capabilities but better runtime performances if you request a new MegaLinter flavor.

MegaLinter is graciously provided by OX Security

skyarkitekten
skyarkitekten previously approved these changes Nov 18, 2023
Copy link

@skyarkitekten skyarkitekten left a 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

@chadcook chadcook self-assigned this Nov 22, 2023
chadcook
chadcook previously approved these changes Nov 22, 2023
verbiage change from essential to required per Cook's suggestion.

Signed-off-by: Josh Nelson <11245067+cloudappsguy@users.noreply.github.com>
Copy link

@skyarkitekten skyarkitekten left a 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.

@skyarkitekten skyarkitekten deleted the 3-create-an-introduction-to-code-reviews-explaining-how-to-make-the-best-of-a-code-review branch January 20, 2024 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create an introduction to Code Reviews explaining how to make the best of a code review
4 participants