Hi Ozoners,

In one of the coffee break chats with a colleague of mine, we realized many
of the PRs in the Ozone project are quite lengthy.

I'm guilty of this myself too. Keeping PR short and sweet is good hygiene.
It allows reviewers to spot potential problems in the code easier, and your
PR is more likely to be reviewed and iterated quickly.

How would you like to see the PR quality improved? I'd like to urge
everyone to break down PRs but I don't necessarily want a GitHub Action
that enforces length limit. :)

Weichiu

Reply via email to