-
Notifications
You must be signed in to change notification settings - Fork 126
Issues: mhagger/git-imerge
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
add support for new Python
pyproject.toml
standard: setup.py install
is deprecated
#208
opened Aug 4, 2023 by
pabs3
Is it possible to redo parts of an iterative merge?
#188
opened Aug 25, 2021 by
BowiFromStackOverflow
Option to keep original commit message in goal=rebase-with-history
#164
opened Sep 14, 2020 by
ravirajkarasulli
imerge sometimes reports a conflict, leaving unmerged files with zero conflicts
#161
opened Sep 10, 2020 by
dabrahams
--goal='rebase' is not yet supported for branches that include merges.
#151
opened Jun 16, 2020 by
abitrolly
Equivalent of the most general case git rebase --onto COMMIT1 COMMIT2 COMMIT3?
#146
opened Apr 4, 2020 by
rulatir
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.