Closed striezel closed 2 years ago
Sorry for the additional merge commit, but that was required to resolve a merge conflict.
Something did not work during the conflict resolution as the diff markers make it in to the content, innit?
What do you mean? I do not see any diff markers here on my end.
But if it is a problem, then I can remove the merge commit.
My apologies, mobile GitHub app made fun of me.
There seem to be merge conflict though
My apologies, mobile GitHub app made fun of me.
Ah, I see.
In the meantime I've removed the merge commit via force push. (Was commit e06b9da0d866b32aa0b6fbf9c0d05bbefadd1778.) Shall I restore it? Or do you want to handle it?
There seem to be merge conflict though
Bad timing on my side. I just remove the merge commit, but restored it now. There should be no conflict now.
Thanks
As I mentioned in my comment reviewing this PR https://github.com/boostorg/gil/pull/670#pullrequestreview-971415430, this change should be reverted as we don't include in RELEASES.md
any changes related to CI, configurations or other trivial chores.
I'm sorry, this merge was my mistake.
Description
This PR adds the changes of #521 to the master branch. It also includes updated release notes. (I hope I got the format right.)
References
See #521 for the original changes.
Since the commit f6a35532f05963804c83f6519955c6fd283a3978 of this PR is a commit from develop, please do not rebase or squash commits when merging. Commit f6a35532 should stay as it is. The intention is to keep master closer to develop, not duplicating commits from develop on master.
Tasklist