Comments by "Brent Jacobs" (@br3nto) on "I’ve Found Something BETTER Than Pull Requests..." video.

  1. I agree with getting code out into prod asap to get feedback, but I’m still still not convinced on the No branch policy. Firstly, just pulling from remote creates a distinct local branch. But more than that, I’m usually working on a few ideas at once, swapping between them over a day. Or checking out other changes from other team members… I don’t know how you could do this without branches…. Maybe with git worktrees… but it’s kinda like working with another branch anyways… further more, doing this my team is still able to deploy multiple times a day… and after, we just rebase and continue. But granted, I don’t know how to get rid of the PR without the equivalent of pair programming before release. But do we need to review in person? Sometimes it’s definitively better, especially for complex changes.
    6
  2. 15:35 how is code “code hidden away on a feature branch” any different from code checked out locally and not pushed to the remote trunk?
    5
  3. 14:39 hold on… the branches should be rebased, and so have all the latest changes…
    3
  4. 13:35 wait what? Local unit tests and integration tests should give you a big clue if your changes are good or not
    1