You want to contribute to an Open Source project, and you have a complex PR to submit. You've tried to keep it small, but sadly getting there took a lot of effort and your branch has more than 30 commits with fixes and reverting of dead ends. You know reviewing this will be a nightmare for the project maintainers, and more importantly, it will be almost impossible for anyone in the future to understand what you did by looking at the history. In this talk we will look at how Git branches work, and how to manicure them using Rebase to build a commit history your colleagues will love you for. _____________________________________________________________ Cloud 66 - Deploy your Rails code directly from your repo to any cloud in minutes. Cloud 66 offers the convenience of Heroku, but on any cloud and in any region, with persistent storage, custom network configuration, zero downtime deployments, blue/green and canary releases, WAF, and more. Get $100 Cloud 66 Free Credits with the code: RailsConf2022 ($100 Cloud 66 Free Credits, for the new user only, valid till 31st December 2022) Cloud 66: https://cloud66.com/frameworks/rails?utm_source=e&utm_medium=d&utm_campaign=ytRailsConf-22