You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Forgive me for barging in here - I have only just discovered this project so I know very little about it, but maybe my tool could help with your automated backports in the cases where cherry-picking causes conflicts due to the commit being backported relying on other commits?
I would certainly not claim that this can always be safely used to fully automate the resolution of conflicts. However it can serve as a useful assistant to a) provide an estimate of the complexity of the porting task and which dependent commits might need to be included in the port.
If I'm off the mark here then feel free to close this, but I thought I'd mention it just in case it's useful :-)
The text was updated successfully, but these errors were encountered:
Forgive me for barging in here - I have only just discovered this project so I know very little about it, but maybe my tool could help with your automated backports in the cases where cherry-picking causes conflicts due to the commit being backported relying on other commits?
https://github.com/aspiers/git-deps#use-case-1-porting-between-branches
I would certainly not claim that this can always be safely used to fully automate the resolution of conflicts. However it can serve as a useful assistant to a) provide an estimate of the complexity of the porting task and which dependent commits might need to be included in the port.
If I'm off the mark here then feel free to close this, but I thought I'd mention it just in case it's useful :-)
The text was updated successfully, but these errors were encountered: