-
Notifications
You must be signed in to change notification settings - Fork 0
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
aa #8
base: master
Are you sure you want to change the base?
aa #8
Conversation
Draft ate nao ser mais draft |
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.
corrige ai
@@ -1,2 +1,4 @@ | |||
|
|||
|
|||
import Integrity from './Integrity' |
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.
apaga tudo
@@ -1,2 +1,4 @@ | |||
|
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.
@FelipeSouzaF olha q foda isso aqui, tu comenda o nome da issue no jira entre [ ] e ele pega a url do jira |
Closes # .
What
Explain the changes you’ve made.
It doesn’t need to be fancy and you don’t have to get to technical, yet.
Just explicit prose on your net change will typically suffice.
Why
The “why” is sometimes more important than the “what” of a code change,
but we tend to put it after the “what” since we aren’t evaluating theory,
we’re evaluating tangible code changes.
How
Of course, the PR diff will tell most of the story of the “how”,
but make sure to draw attention to the significant design decisions.
You decided to write a recursive method instead of a loop,
pointing out the merits of this will help the reviewer understand
your reasoning and in turn provide a better review.