2 ms·

Meaning, PRs are generally bad to require to do a build?

• bobthepanda 4y ago
  In my experience it is a good idea to try and keep code reviews and pull requests short and sweet. It’s much easier to review small concise code than mega commits, it’s much easier to catch mistakes in them, and being set up to iterate small changes quickly tends to result in faster velocity (as opposed to people trying to avoid reviewing the mammoth, scary block of code that might take a half hour of reading to just read it, rather than review it.)