Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is that a common usecase?

I think the way I would do it, is to go to target branch, cherry pick the commits and push. Then go to source branch and revert the changes. All done from within the IDE. Not the cleanest way, though.



Incredibly common when you write code faster than your colleague or manager can review them. You always have lots of branches and sometimes the branches implement interrelated functionality.


Interesting. Why not keep on a merge branch before review?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: