Reinstate changes lost due to automatic merging
The automatic merging code used `--strategy=ours`, which turned out to be incorrect; instead we wanted `--strategy=recursive --strategy-option=ours`. This small difference results in merging throwing away _all_ EE changes in favour of CE changes, instead of only doing this for conflicts. This commit ensures that EE has all the appropriate changes. The diff was generated by cherry picking all merge commits made since two days ago, picking them with `--strategy=recursive --strategy-option=ours`.
Showing
... | ... | @@ -287,6 +287,7 @@ gem 'webpack-rails', '~> 0.9.10' |
gem 'rack-proxy', '~> 0.6.0' | ||
gem 'sass-rails', '~> 5.0.6' | ||
gem 'sass', '~> 3.5' | ||
gem 'uglifier', '~> 2.7.2' | ||
gem 'addressable', '~> 2.5.2' | ||
... | ... |
app/models/ci/bridge.rb
0 → 100644
This diff is collapsed.
... | ... | @@ -159,6 +159,10 @@ |
"karma-webpack": "^4.0.0-beta.0", | ||
"nodemon": "^1.18.4", | ||
"prettier": "1.15.2", | ||
"vue-jest": "^3.0.1", | ||
"webpack-dev-server": "^3.1.10" | ||
}, | ||
"engines": { | ||
"yarn": "^1.10.0" | ||
} | ||
} |
spec/factories/ci/bridge.rb
0 → 100644
File moved
This diff is collapsed.
Please register or sign in to comment