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

Merging master into 2-0-stable (one month of commits in master) #2639

Merged
merged 163 commits into from
Sep 5, 2018

Conversation

luisramos0
Copy link
Contributor

@luisramos0 luisramos0 commented Sep 3, 2018

What? Why?

Merging master into 2-0-stable.

This is the result of:
git checkout master
git pull upstream master
git checkout 2-0-stable
git pull upstream 2-0-stable

git checkout -b 2-0-stable-sept
git merge master

  • resolved conflicts
    git add spec/controllers/spree/orders_controller_spec.rb
    git add Gemfile
    git add Gemfile.lock

git commit
git push origin 2-0-stable-sept

The last commit of the last merge into 2-0-stable was on the 27th July, so this one looks good as it starts on the following commit on the 30th July and then goes up to the 4th of September.

mkllnk and others added 30 commits July 30, 2018 14:28
And formatted for easier reading and writing.
This should prevent issues like openfoodfoundation#2427.

Also converted comments into HTML syntax so that you don't have to delete them when creating a PR.
…-fork-version

Update Spree's fork revision in Gemfile
This is more appropriate, and allows changes the separate route files to
be loaded automatically in the development environment.
The methods :update! and :update (to replace :update_attributes! and
:update_attributes) were not added until Rails 4.

See this for more information:
https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Rails/ActiveRecordAliases
…isable_rubocop_cop_rails_activerecordaliases

Disable rubocop cop "Rails/ActiveRecordAliases"
We don't need to visit the admin dashboard before each spec.
On my machine:

  54 seconds before
  47 seconds after
  speed up by 13%
Enterprises can be in different order. Using `with_options` doesn't
care about the order.
From 18s to 12s: 33% speed up
The code has been inactive since 2015 and was probably obsolete anyway.
From 1.9s to 1.7s.
From 68 to 63 seconds.
From 80s to 74s.
luisramos0 and others added 8 commits September 2, 2018 22:13
…pendabot/bundler/eventmachine-1.2.7

Bump eventmachine from 1.2.3 to 1.2.7
…pendabot/bundler/foreigner-1.7.4

Bump foreigner from 1.6.1 to 1.7.4
…tter_policy_page

[Cookies] Updated cookies policy page text
…der_link_in_subscription_emails_unless_user

Subscription emails for customer should not link to order page if customer has no user account
…pendabot/bundler/angular-rails-templates-0.3.0

Bump angular-rails-templates from 0.2.0 to 0.3.0
…d_code

Removed old files that were used with, now unsupported, heroku
…nner_bug

[Cookies] Added new test to cookies spec to cover bug on cookies banner and fix…
@luisramos0 luisramos0 changed the title 2 0 stable sept Merging master into 2-0-stable (one month of commits in master) Sep 3, 2018
…nner_font_size

[Cookies] Increased cookies banner font size for med/large screens to improve readability
@daniellemoorhead
Copy link
Contributor

@luisramos0

Please, please, #assignyourself, please! 🙏

@luisramos0
Copy link
Contributor Author

one comment/question is: with local git log I see only one commit with the full merge, here in GH it shows all the 160 separate commits...

@sauloperez
Copy link
Contributor

These are all the commits we're bringing in from master, those that weren't in 2-0-stable, so I think it's all right.

@luisramos0
Copy link
Contributor Author

luisramos0 commented Sep 4, 2018

I found a problem in the Gemfile, stripe should have been 3.3.2. It was a mistake in my conflict resolution.
SO, I went through every conflict resolution again in this PR and made sure bundle install works at the end. Much better now on the Gemfile.lock.

  • I picked two more updates that Hugo had done on the 2-0- branch (climate_control and stringex)
  • Fixed rabl (0.8.4) and highline (1.6.18) from spree_core v2

@sauloperez
Copy link
Contributor

can we merge it then @luisramos0 ?

@luisramos0
Copy link
Contributor Author

I was just waiting 2 approvals as a normal PR.

@sauloperez
Copy link
Contributor

I thought we consider it one of those no-review PRs but it's fine.

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

Successfully merging this pull request may close these issues.