<commit_before># Glimpse::Git

Provide a glimpse into the Git info of your Rails application.

Things this glimpse view provides:

- View the current branch name
- Compare the diff of the current revision on your GitHub repo

## Installation

Add this line to your application's Gemfile:

    gem 'glimpse-git'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install glimpse-git

## Usage

Add the following to your `config/initializers/glimpse.rb`: 

```ruby
Glimpse.into Glimpse::Views::Git
```

You will need to set the GitHub project's name with owner if you plan on
comparing the current ref against your default branch on GitHub.

```ruby
# nwo - name with owner - owner/name
Glimpse.into Glimpse::Views::Git, :nwo => 'dewski/json_builder'
```

You can also manually set each of the following optional options:

- SHA
- Default Branch (master by default)
- Branch Name

```ruby
Glimpse.into Glimpse::Views::Git, :sha => '740f6b7b11b8717efaf51ddb98ce23394544f7e0', :default_branch => 'rails4.0', :branch_name => 'integration'
```

## Using Glimpse::Git on Heroku

If you try to deploy this to Heroku it won't actually work right away. Heroku
removes the .git directory which doesn't allow us to fetch the HEAD ref or branch.

To solve this, there is a custom buildpack that is forked from the default Ruby
buildpack that will set `GIT_SHA` and `GIT_BRANCH` for you.

To install this buildpack just run:

```
heroku config:set BUILDPACK_URL=https://github.com/dewski/heroku-buildpack-ruby.git --app appname
```

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request<commit_msg>Update README about Heroku notice<commit_after># Glimpse::Git

Provide a glimpse into the Git info of your Rails application.

Things this glimpse view provides:

- View the current branch name
- Compare the diff of the current revision on your GitHub repo

## Installation

Add this line to your application's Gemfile:

    gem 'glimpse-git'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install glimpse-git

## Usage

Add the following to your `config/initializers/glimpse.rb`:

```ruby
Glimpse.into Glimpse::Views::Git
```

You will need to set the GitHub project's name with owner if you plan on
comparing the current ref against your default branch on GitHub.

```ruby
# nwo - name with owner - owner/name
Glimpse.into Glimpse::Views::Git, :nwo => 'dewski/json_builder'
```

You can also manually set each of the following optional options:

- SHA
- Default Branch (master by default)
- Branch Name

```ruby
Glimpse.into Glimpse::Views::Git, :sha => '740f6b7b11b8717efaf51ddb98ce23394544f7e0', :default_branch => 'rails4.0', :branch_name => 'integration'
```

## Using Glimpse::Git on Heroku

Unfortunately Heroku [removes](https://devcenter.heroku.com/articles/slug-compiler#compilation)
the .git directory during slug compilation which doesn't make it possible to
view the current deployed SHA or branch.

The one workaround is to set the GIT_SHA and GIT_BRANCH ENV variables within
your deploy process.

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
{'fraction_non_alphanumeric': 0.09006928406466513, 'fraction_numerical': 0.018475750577367205, 'mean_word_length': 4.338983050847458, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 11, 'https://': 2, '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': '1387322', 'n_tokens_mistral': 1146, 'n_tokens_neox': 1071, 'n_words': 446}