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.

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

When conflicts have been previously detected ensure that they can be resolved #19247

Merged
merged 4 commits into from
Mar 29, 2022

Commits on Mar 29, 2022

  1. When conflicts have been previously detected ensure that they can be …

    …resolved
    
    There is yet another problem with conflicted files not being reset when
    the test patch resolves them.
    
    This PR adjusts the code for checkConflicts to reset the ConflictedFiles
    field immediately at the top. It also adds a reset to conflictedFiles
    for the manuallyMerged and a shortcut for the empty status in
    protectedfiles.
    
    Signed-off-by: Andrew Thornton <art27@cantab.net>
    zeripath committed Mar 29, 2022
    Configuration menu
    Copy the full SHA
    7aad0a7 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    de7088b View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    e878d77 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    585ae3c View commit details
    Browse the repository at this point in the history