Fixed XOR usage in the object merge helper to output warnings correctly.

[DanielRuf]

Description

This PR fixes the XOR (before this the secon value was always the same).
See also http://www.howtocreate.co.uk/xor.html

Type of change

Please add an "x" into the option that is relevant:

• Bug Fix 🐛 (non-breaking change which fixes an issue)
• Enhancement 🚀 (non-breaking change which adds functionality)
• Breaking Change 💥 (fix or feature that would cause existing functionality to not work as expected)
• Polish 💅 (Just some cleanups)
• Internal 🏠 Only relates to internal processes.

[DanielRuf]

Fixed XOR usage in the object merge helper to output warnings correctly.

Short question, why do you use the past form? Git recommends using imperative form so commits will apply to the following rule:

If this commit is applied it will ... fix XOR usage ...

Fixed is imho not correct ;-)

[SG-Noxoreos]

Short question, why do you use the past form? Git recommends using imperative form...

Because the automated changelog build script uses this text as well as the labels to format the changelog entry.
Commit messages are not the same as the pull request title.

[DanielRuf]

Ah ok, thanks for the clarification =)

[DanielRuf]

Might be useful to document this in CONTRIBUTING.md.