<commit_before>article.section
  .wrap
    h1.section__header.header.header--beta Getting started
    .grid.grid--line
      .grid__cell.unit-1-2.content
        markdown:
          ## Bundler

          Add `http://rails-assets.org` as a&nbsp;new source, then reference any Bower components that you need as gems in the&nbsp;following&nbsp;convention:

              gem 'rails-assets-BOWER_PACKAGE_NAME'

          During `bundle` `install`, if Bundler requests a&nbsp;package like this, Rails Assets’ daemon automatically&nbsp;will:

          * fetch the component from Bower’s&nbsp;registry,
          * analyze its manifest file, `bower.json`,
          * repackage the component as a&nbsp;valid&nbsp;Ruby gem and&nbsp;serve&nbsp;it to your application.

          Dependencies are handled the&nbsp;same way&nbsp;recursively.

      .grid__cell.unit-1-2
        = render 'shared/diff_gemfile'
    .grid.grid--line
      .grid__cell.unit-1-2.content
        markdown:
          ## Asset pipeline

          You can `require` any asset that’s exposed as&nbsp;`main` in&nbsp;component’s manifest file.

          Gems created by Rails Assets work great with any Sprockets-based application.

        p.notice.notice--important.content--small
          strong> Notice:
          | Rails Assets is not production-ready&nbsp;yet.
      .grid__cell.unit-1-2
        = render 'shared/diff_javascript'
        = render 'shared/diff_stylesheet'<commit_msg>Remove the production-unready notice<commit_after>article.section
  .wrap
    h1.section__header.header.header--beta Getting started
    .grid.grid--line
      .grid__cell.unit-1-2.content
        markdown:
          ## Bundler

          Add `http://rails-assets.org` as a&nbsp;new source, then reference any Bower components that you need as gems in the&nbsp;following&nbsp;convention:

              gem 'rails-assets-BOWER_PACKAGE_NAME'

          During `bundle` `install`, if Bundler requests a&nbsp;package like this, Rails Assets’ daemon automatically&nbsp;will:

          * fetch the component from Bower’s&nbsp;registry,
          * analyze its manifest file, `bower.json`,
          * repackage the component as a&nbsp;valid&nbsp;Ruby gem and&nbsp;serve&nbsp;it to your application.

          Dependencies are handled the&nbsp;same way&nbsp;recursively.

      .grid__cell.unit-1-2
        = render 'shared/diff_gemfile'
    .grid.grid--line
      .grid__cell.unit-1-2.content
        markdown:
          ## Asset pipeline

          You can `require` any asset that’s exposed as&nbsp;`main` in&nbsp;component’s manifest file.

          Gems created by Rails Assets work great with any Sprockets-based application.

      .grid__cell.unit-1-2
        = render 'shared/diff_javascript'
        = render 'shared/diff_stylesheet'
{'fraction_non_alphanumeric': 0.09419770773638969, 'fraction_numerical': 0.0064469914040114614, 'mean_word_length': 2.6509803921568627, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7529604', 'n_tokens_mistral': 836, 'n_tokens_neox': 785, 'n_words': 212}