Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use merge-base (three dot diff) instead of direct diff (#1653) (#1654) #1655

Merged
merged 4 commits into from
Jan 27, 2022
Merged

Use merge-base (three dot diff) instead of direct diff (#1653) (#1654) #1655

merged 4 commits into from
Jan 27, 2022

Commits on Jan 26, 2022

  1. Use merge-base (three dot diff) instead of direct diff for git-diff-a… 

    …se (infection#1653) (infection#1654)

* Use merge-base (three dot diff) instead of direct diff for git-diff-base (infection#1653)

* Add command line dumping for debugging

* Fetch full history to allow finding common ancestor, not just last commit

* Remove var_dumps

* Debug with git depth 1

* Fall back to direct diff if merge base commit is not avialable

* Restore deep git fetch

* Kill UnwrapTrim mutant
    @bdsl
    bdsl committed Jan 26, 2022
    Configuration menu
    Copy the full SHA
    534bec8 View commit details
    Browse the repository at this point in the history

  2. Fix php parse error

    @bdsl
    bdsl committed Jan 26, 2022
    Configuration menu
    Copy the full SHA
    2e73331 View commit details
    Browse the repository at this point in the history

  3. Add test_it_falls_back_to_direct_diff_if_merge_base_is_not_availabe

    @bdsl
    bdsl committed Jan 26, 2022
    Configuration menu
    Copy the full SHA
    80b3c73 View commit details
    Browse the repository at this point in the history

  4. Skip test on Windows

    @bdsl
    bdsl committed Jan 26, 2022
    Configuration menu
    Copy the full SHA
    3c4a83d View commit details
    Browse the repository at this point in the history