-
Notifications
You must be signed in to change notification settings - Fork 56
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
Conversation
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? |
Release 3.1.0
Release 3.1.1
Release version 3.1.2
Release 3.1.3
* 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]>
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 |
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. |