Make your Pull Requests clear and obvious to anyone viewing them.
Set main as your target branch.
Use Conventional Commits principles in naming PRs and branches:
Feat: ...for new features and new functionality implementations.Bug: ...for bug fixes.Fix: ...for minor issues fixing, like typos or inaccuracies in code.Chore: ...for boring stuff like code polishing, refactoring, deprecation fixing etc.
PR naming example: Feat: Add Threads API handling or Bug: Fix message result duplication
Branch naming example: feat/add-threads-API-handling or bug/fix-message-result-duplication
-
What
...
-
Why
...
-
Affected Areas
...
-
More Info
...
We'll appreciate you including tests to your code if it is needed and possible. ❤️