Smaïne Milianni
@SmaineDev
SEPTEMBER 15 -16, 2022 - LILLE, FRANCE & ONLINE
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
The title and commit message should explain the changes
Description can contain things such as screenshots, videos, gifs, etc.
Before / After comparison
Any details that help reviewers to have a better understanding
@SmaineDev
@SmaineDev
Technical details about the implementation
@SmaineDev
@SmaineDev
✂️ Separate feature and refactoring
⭕️ Focus on the purpose of the PR
🧩 Split in commit if needed
@SmaineDev
🔨 Test the new code
😅 Ensure not to break existing tests
@SmaineDev
🗣 Comment changes yourself
🔦 Highlight interesting/critical part
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
Open ticket/Figma, check tests, ask teammate...
@SmaineDev
SOLID, KISS, DRY, YAGNI...
@SmaineDev
👋🏽 Approve a PR is giving consent 🖊 and engaging your responsibility
@SmaineDev
Endpoint, Security, Business rules...
@SmaineDev
Anticipate edge case, architecture layer,
Behavior in case of errors,
Exception handling
Performance, logs...
@SmaineDev
Jump from class to class, check that most of the use cases are tested, complexity, consistency...
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
## What
(Summarize the feature/bug)
## Why
[link to ticket/issue](www.jira_is_a_nightmare/project/42)
## How to?
## Relevant logs and/or screenshots
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev
@SmaineDev