Thread: Do you even trunk? 🧳
The idea that a whole development team shares a single branch as the only source of truth regarding the application state is sometimes seen as scary and revolutionary.
Granted, moving to trunk-based development requires a leap of faith from developers who, for so long, have enjoyed the comfort zone of long-living branches and asynchronous work.
1. Aggressively limit the scope of your pull requests. Keep doing this until you can't write any smaller changesets reasonably.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!