Skip to content

Conversation

@zkraus
Copy link
Contributor

@zkraus zkraus commented Oct 16, 2025

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.

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

@averevki averevki left a 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 👍

Copy link
Contributor

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

Copy link
Contributor

@averevki averevki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^

Copy link
Contributor

@emmaaroche emmaaroche left a 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 😄

Comment on lines +24 to +26
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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Copy link
Contributor

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

@averevki
Copy link
Contributor

@zkraus @azgabur hey, are you still working on this PR?

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.

4 participants