diff options
| author | Gleb Mazovetskiy <glex.spb@gmail.com> | 2014-04-19 15:25:07 +0400 |
|---|---|---|
| committer | Gleb Mazovetskiy <glex.spb@gmail.com> | 2014-04-19 15:25:07 +0400 |
| commit | 4ae14a582bfb37e9af7827eddee28807b87f0663 (patch) | |
| tree | 42a852f44f7b12c7fa7411e8aa81945462432073 | |
| parent | 1a4ff080af2be55f1c17b5d2c99eb5f31aaf2e97 (diff) | |
readme: link issues [ci skip]
| -rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -28,8 +28,9 @@ If you must use it, make sure bootstrap-sass is moved out of the `:assets` group This is because, by default in Rails 3.2, assets group gems are not required in `production`. However, for pre-compilation to succeed in production, `bootstrap-sass` gem must be required. -Starting with bootstrap-sass v3.1.1.1, due to the structural changes from upstream you will need -backported asset pipeline gems on Rails 3.2. There is more on why this is necessary in #523 and #578. +Starting with bootstrap-sass v3.1.1.1, due to the structural changes from upstream you will need these +backported asset pipeline gems on Rails 3.2. There is more on why this is necessary in +https://github.com/twbs/bootstrap-sass/issues/523 and https://github.com/twbs/bootstrap-sass/issues/578. ```ruby gem 'sprockets-rails', '=2.0.0.backport1' |