Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I like how the second paragraph explains the whole first paragraph.
Also, whiskey. Or tequila (always 100% agave). -
mundo0349796yNever push to master or develop only merge requests.
Work on branches from develop only, these branches should be specific features only, atomic changes, atomic commits.
So, work on pussy, branch pussy, merge to pussy, merge request to dev.
Dick should be another feature for dev.
Dick and pussy never touch, sadly
Related Rants
if i work on PussyBranch to build up a feature, and DickBranch is my main branch so if i merge directly from Pussy into Dick and then work on Dick, and then switch to Pussy again then surely i wouldnt be able to commit to Dick because Pussy isn't filled up with the new code, right? I'd need to pull the latest code from Dick into Pussy branch. but what if i dont want to merge Dick into Pussy code? because what Dick contains, Pussy should not and that would cause anomaly and break uhh how do u call it, the purpose of the branch itself right. So if I want to work only on Pussy and commit just that segment of the new code into Dick, how do I do that? Do i have to force pushing Pussy code into Dick every time or can i do it without force command? serious answers only pls
also what alcohol is good for a more productive and longer hour coding sessions thx
question
2 questions
git