-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
feat: update with master #361
feat: update with master #361
Conversation
Co-authored-by: Sergio Moya <[email protected]>
# Conflicts: # package-lock.json # package.json
Kudos, SonarCloud Quality Gate passed! |
Remember to merge this as regular commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: This should be merged with "Rebase and merge", otherwise the commits will be lost.
@derberg how should we proceed since that method is disabled?
I mark this as "Request changes" to block the merge.
I think the best still is keeping a PR always opened from |
@smoya you will have to change the settings of the branch and then change it back 🙂
Its not possible because of conflicts in package version. Have to happen manually. It only works if the branch is not doing it's own deployment and version change. |
I thought that wasnt allowed to me. But it is. So proceeding.
Yeah, right. The never ending story. |
I dont fully get why squash and merge works but Rebase doesnt. Do you believe there are conflicts? Can you rebase and push? |
I have always used merge commit, so not sure what the deal is with rebase and merge. |
🎉 This PR is included in version 5.0.0-next-major-spec.18 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 6.0.0-next-major-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
This PR updates
next-major-spec
with master.