Closed Zinka010 closed 4 years ago
Yeah, I realize my PR's are way too big, but its mostly just because I just end up making them at the end of a day of tuning many different things. I'm not sure if there's an efficient way to make multiple changes that rely on each other and also be able to quickly switch what I'm working on based on a shift in drive team and mentor requests. I'd appreciate any advice on it since I agree that this makes issues much harder to pinpoint.
Totally fair and if this is what works best for you to handle the chaos then I support you fully!
One way I handle changes that depend on each other is to create cascading branches, e.g. master -> isolated_change_1 -> isolated_change_2 -> isolated_change_3, where each branch has individual changes. Then you merge isolated_change_1 to master first, after it is merged, isolated_change_2 base branch can change to master, and so on. I can show you what I mean on Wed if you want to learn more.
Maybe not Wednesday since I'm still swamped with stuff to do but I'd love to after Carleton
Further tuning of the competition robot robot