A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/peek/peek-git below:

peek/peek-git: Take a peek into the Git info of your Rails application.

Take a peek into the Git info of your Rails application.

Things this peek view provides:

Add this line to your application's Gemfile:

And then execute:

Or install it yourself as:

Add the following to your config/initializers/peek.rb:

Peek.into Peek::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.

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

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

Peek.into Peek::Views::Git, \
  :sha => '740f6b7b11b8717efaf51ddb98ce23394544f7e0',
  :default_branch => 'rails4.0',
  :branch_name => 'integration',
  :domain => 'github.com',
  :protocol => 'https'
Using Peek::Git on Heroku

Unfortunately Heroku removes 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.

  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

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4