GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [ticket/17732] Report real merge conflicts in the automatic updater by dmzx · Pull Request #7068 · phpbb/phpbb

Conversation

@dmzx

@dmzx dmzx commented Sep 29, 2026

Copy link
Copy Markdown

Checklist:

  • Correct branch: master for new features; 3.3.x for fixes
  • Tests pass
  • Code follows coding guidelines: master and 3.3.x
  • Commit follows commit message format

Tracker ticket:

https://tracker.phpbb.com/browse/PHPBB-17732

Since #6216 (PHPBB-16570) a file with a real merge conflict is treated as already merged and silently left out of the update. There are two causes in diff_files.php:

  1. The in_array() check is inverted, so a conflict is never added to the list on a first run.
  2. On a first run, merged_orig_output() (the board side of every conflict) equals the board file whenever all of phpBB's changes to that file conflict. So $empty is true and the conflict is skipped even with !in_array().

A conflicted file now only counts as merged by the user on a later run, when it is already in the conflict list. Otherwise it is added to the list.

tests/installer/diff_files_test.php runs the real diff_files task on fixtures:

  • a pure conflict;
  • a conflict plus a non-conflicting phpBB change;
  • a conflict kept by the user on a later run;
  • a clean three-way merge;
  • a file already equal to the new version.

Both conflict cases fail without the fix.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@dmzx
[ticket/17732] Report real merge conflicts in the automatic updater
7c981cf
A file with a real merge conflict was treated as already merged by the
user and silently left out of the update: the in_array() check was
inverted, and on a first run merged_orig_output() always equals the
board file when all changes conflict. Only a file that is already in
the conflict list can now count as merged by the user.

PHPBB-17732
@github-actions

github-actions Bot commented Sep 29, 2026

Copy link
Copy Markdown

The attempt to merge branch 3.3.x into master has completed after considering the changes in this PR.

  • Merge result: Conflict ❌

A separate PR will be needed to merge 3.3.x into master.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dmzx dmzx mentioned this pull request Sep 30, 2026
[ticket/17732] Report real merge conflicts in the automatic updater -- master version #7070
Open
4 tasks done
@marc1706 marc1706 added this to the 3.3.21 milestone Nov 4, 2026
@marc1706 marc1706 added the 3.3 (Proteus) 🌑 label Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

3.3 (Proteus) 🌑

Projects

None yet

Milestone

3.3.21

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@dmzx @marc1706
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.