-
Notifications
You must be signed in to change notification settings - Fork 23
ADD: DESIGN_GUIDE.md #794
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
base: main
Are you sure you want to change the base?
ADD: DESIGN_GUIDE.md #794
Conversation
Design guide is suppose to be a set of guidelines and tips on how to desing tests, write commits, submit a review PRs, and anything that might be usefull.
averevki
left a comment
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.
Maybe something we can convert to project's claude.md context file down the road. LGTM now 👍
averevki
left a comment
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.
@zkraus sign-off the commit when you're done please. CI won't allow PR to merge without it
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.
^
emmaaroche
left a comment
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 a few small suggestions to add to the Commits and Creating PRs sections, feel free to apply, modify, or decline them as you see fit 😄
| 1. To promote quality code, request 2 reviewers | ||
| 1. Link relevant issues, and/or summarize the changes | ||
| 1. Consider providing a verification steps in the PR description (might have a tool for that) |
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.
| 1. To promote quality code, request 2 reviewers | |
| 1. Link relevant issues, and/or summarize the changes | |
| 1. Consider providing a verification steps in the PR description (might have a tool for that) | |
| 1. To promote quality code, request 2 reviewers | |
| 1. Link relevant issues, and/or summarize the changes | |
| 1. Consider providing a verification steps in the PR description (might have a tool for that) | |
| 1. Ensure CI checks pass before opening a PR (e.g., DCO sign-off, code analysis, GitGuardian) | |
| 1. Use a draft PR to share work in progress and gather early feedback before marking it ready for review |
|
|
||
| ## Commits | ||
|
|
||
| 1. Consider using https://www.conventionalcommits.org/en/v1.0.0/ (.gitmessage) |
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.
| 1. Consider using https://www.conventionalcommits.org/en/v1.0.0/ (.gitmessage) | |
| 1. Consider using https://www.conventionalcommits.org/en/v1.0.0/ (.gitmessage) | |
| 1. Run `make reformat` and `make commit-acceptance` locally to catch code analysis or formatting issues before committing and pushing | |
| 1. Sign off commits by adding the `-s` flag (`git commit -s`) | |
| 1. Optionally, sign commits with the `-S` flag (`git commit -S`) if you have a GPG or SSH key configured — this verifies commit authenticity on GitHub |
azgabur
left a comment
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.
Want to review/collaborate before merge, just need to find time
This is a team wide open PR, please do suggest addition, edits, anything that you thing might be useful for this guide.
Design guide is suppose to be a set of guidelines and tips on how to design tests, write commits, submit a review PRs, and anything that might be useful.