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

Merge master to dev to resolve conflicts #109

Merged
merged 6 commits into from
Sep 14, 2024
Merged

Conversation

Hlavtox
Copy link
Contributor

@Hlavtox Hlavtox commented Sep 14, 2024

Questions Answers
Description? Release 3.2.0 has some conflicts, this is a branch merging changes from master into dev, should resolve it.
Type?
BC breaks?
Deprecations?
Fixed ticket?
Sponsor company
How to test?

Progi1984 and others added 6 commits June 1, 2020 15:57
* Remove useless Google Analytics parameters

* Delete PULL_REQUEST_TEMPLATE.md

* Update build-release.yml

* Update README.md

* Update README.md

* feat: remove mobile desactivation

* Release 3.1.4

---------

Co-authored-by: JoseNOM <[email protected]>
Co-authored-by: Mathieu Ferment <[email protected]>
Co-authored-by: leemyongpakvn <[email protected]>
Co-authored-by: Krystian Podemski <[email protected]>
Co-authored-by: florine2623 <[email protected]>
Co-authored-by: Daniel Hlavacek <[email protected]>
Co-authored-by: Guyomar Alexis <[email protected]>
@ShaiMagal ShaiMagal merged commit d17c68a into PrestaShop:dev Sep 14, 2024
9 checks passed
@Hlavtox Hlavtox added this to the 3.2.0 milestone Sep 14, 2024
@matks matks changed the title Merge lalala to dev to resolve conflicts Merge master to dev to resolve conflicts Sep 15, 2024
@matks
Copy link
Contributor

matks commented Sep 15, 2024

I see you used my suggestion for the name of the branch 😄 congrats on your first branch merge

This is what we do every week in PRs like PrestaShop/PrestaShop#36551

@Hlavtox
Copy link
Contributor Author

Hlavtox commented Sep 15, 2024

@matks Yes! It worked, thank you! :-)

Fun fact - #108 got merged automatically somehow together with this PR, even if we did not click it. Any idea why? 😁

@matks
Copy link
Contributor

matks commented Sep 15, 2024

@matks Yes! It worked, thank you! :-)

Fun fact - #108 got merged automatically somehow together with this PR, even if we did not click it. Any idea why? 😁

Because GitHub considers that a PR is merged when the commits of its source branch have been added to the target branch. A Pull Request is simply a request to transfer commits from one branch to another, with some metadata (labels, messages, body...). It has no specific status, it's the commits status which is acknowledged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

7 participants