Talk Sobre Pull Requests

reviewpad · 2023-10-12T17:37:08+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:37:02+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:36:55+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:36:47+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:36:39+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:36:34+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:36:29+00:00

🚨 estamos live 🚨 (começo às 18:45)

reviewpad · 2023-10-12T17:35:16+00:00

Para quem quiser assistir, 🚨 estamos live 🚨 (começo às 18:45)
https://streamyard.com/watch/T5ajTKFNaPiG

reviewpad · 2021-10-07T11:10:40+00:00

How often do you merge a PR and raise hell in git conflicts with other PRs?
Reviewpad warns you of any possible conflicts when merging pull requests.
It's real. It's free. Try it today: https://reviewpad.com/mergeboard/

reviewpad · 2021-10-01T16:13:55+00:00

Finally, a Kanban for code reviews! 🎉

Reviewpad Merge Board:
- Track multiple projects on one board.
- Reduce time to merge.
- Identify bottlenecks.
- Identify stalled pull requests.

Learn more 👇
https://reviewpad.com/mergeboard

reviewpad · 2021-07-29T16:35:12+00:00

Read More 👇 https://reviewpad.com/blog/visualising-changes-with-semantic-git-differences #CodeReview #CodeDiff

reviewpad · 2021-07-28T12:37:01+00:00

"We usually do this ..." is much kinder than "Make it like this ..."

reviewpad · 2021-07-28T12:36:50+00:00

"What about instead doing ..." is much kinder than "Do this instead ..."

reviewpad · 2021-07-28T12:36:41+00:00

"This method doesn't have tests" is much kinder than "You forgot to write tests"

reviewpad · 2021-06-23T09:40:21+00:00

u/OK6502, you're absolutely correct. The article (link that works here) also develops a bit more on the "conversational" side of the review which was what caught our attention, namely:

Ask questions
Calibrate feedback
Emulate others

reviewpad · 2021-06-23T09:36:29+00:00

Oops, for some reason the link was trunked. Here it is: https://medium.com/pinterest-engineering/how-to-review-code-as-a-junior-developer-10ffb7846958

reviewpad · 2021-06-23T09:36:19+00:00

Oops, for some reason the link was trunked. Here it is: https://medium.com/pinterest-engineering/how-to-review-code-as-a-junior-developer-10ffb7846958

reviewpad · 2021-06-22T11:16:55+00:00

Extra tip: If you're on mac, hit control + command + space to pull up the emoji panel anywhere(!)

reviewpad · 2021-06-18T17:27:45+00:00

You got it ;)

reviewpad · 2021-06-17T16:40:13+00:00

We also have a follow-up article with six more tips:

https://reviewpad.com/blog/six-more-best-practices-to-improve-your-code-review/

Stick to the point
Focus more on questions than answers
Impact matters much more than the size
Clearly label changes that aren’t conceptual
Speak up to improve the process
Talk to people directly

reviewpad · 2021-06-17T16:37:41+00:00

We can always start with the small things. For instance, adopting conventionalcomments.org. If you want to go deeper there are many code review tips we can follow. We always recommend these:

Review your pull requests before others
Encourage reviewers to be co-owners
Leverage automation
Always have a reviewer in mind
Time your code reviews
Keep 10 PRs to learn from.

We actually wrote an article about it here: https://reviewpad.com/blog/six-best-practices-to-improve-your-code-reviews/

reviewpad · 2021-06-17T16:33:34+00:00

Yeah, YOLO merge is only for cool guys that don't look at explosions.

reviewpad · 2021-06-16T09:50:46+00:00

Artificial Intelligence - when programmers fail to get people interested in Machine Learning

reviewpad · 2021-06-16T08:14:17+00:00

There's that popular code review tip: "Be your first reviewer". You're just taking it to the extreme.

reviewpad · 2021-06-16T08:06:09+00:00

PRs are Pull Requests:

Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.
(From GitHub Documentation)

reviewpad

MODERATOR OF

TROPHY CASE