Simple Git Workflow for Effective Teams
Simple Git Workflow for Effective Teams
Hi HN, My friends and I worked at Meta & Google. Once we’d left we realised a lot of the internal tooling didn’t have parity on the outside. Specifically, version control tools outside big tech are much harder to use than Google’s Critique and Facebook’s Phabricator, etc. Git is powerful but notoriously difficult to use [0]. Existing Git clients don’t make life much easier, exposing all the complexity by default. In practice we don’t need an equally complex GUI, and version control can be much easier to use. In our experience, it works best to expose a small number of features for an efficient workflow: commit, submit changes for review, and rebase (those are actively used in trunk-based development). Further, a “tree of commits” is a sufficient mental model, there’s no need to worry about branches, merges, etc. We have built a simple prototype called TrunkFlow that works inside Visual Studio Code. It borrows UI from Sapling (which is similar to internal tooling at Meta) but is fully compatible with Git. Would appreciate any feedback on the prototype [1] or on the challenges you’ve had using Git! [0]: https://news.ycombinator.com/item?id=25121416 [1]: https://www.trunkflow.com/
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
A simple Git workflow demonstration under Windows
A simple Alfred 4 Fantastical workflow
Beeminder for Effective Charities
Building a simple and effective packet sniffer in Golang
The platform that teams use to conduct effective retros
Simple and effective stretch app
Git Auto – Automate Your Git Workflow
Simple and Effective SSL Certificate Monitoring
Simple yet unreasonably effective recipe to tackle burnout
I wrote a simple book on Git