|
1 | 1 | [](https://badge.fury.io/rb/overcommit)
|
2 |
| -[](https://travis-ci.org/brigade/overcommit) |
3 |
| -[](https://ci.appveyor.com/project/brigade/overcommit/branch/master) |
4 |
| -[](https://coveralls.io/github/brigade/overcommit?branch=master) |
5 |
| -[](https://codeclimate.com/github/brigade/overcommit) |
6 |
| -[](http://inch-ci.org/github/brigade/overcommit) |
| 2 | +[](https://travis-ci.org/sds/overcommit) |
| 3 | +[](https://ci.appveyor.com/project/sds/overcommit/branch/master) |
| 4 | +[](https://coveralls.io/github/sds/overcommit?branch=master) |
| 5 | +[](https://codeclimate.com/github/sds/overcommit) |
| 6 | +[](http://inch-ci.org/github/sds/overcommit) |
7 | 7 |
|
8 | 8 | <p align="center">
|
9 |
| - <img src="https://raw.githubusercontent.com/brigade/overcommit/master/logo/horizontal.png" width="65%" alt="Overcommit Logo"/> |
| 9 | + <img src="https://raw.githubusercontent.com/sds/overcommit/master/logo/horizontal.png" width="65%" alt="Overcommit Logo"/> |
10 | 10 | </p>
|
11 | 11 |
|
12 | 12 | `overcommit` is a tool to manage and configure
|
13 | 13 | [Git hooks](http://git-scm.com/book/en/Customizing-Git-Git-Hooks).
|
14 | 14 |
|
15 |
| - |
| 15 | + |
16 | 16 |
|
17 | 17 | In addition to supporting a wide variety of hooks that can be used across
|
18 | 18 | multiple repositories, you can also define hooks specific to a repository which
|
@@ -60,7 +60,7 @@ This project aims to support the following Ruby runtimes on both \*nix and Windo
|
60 | 60 |
|
61 | 61 | Some of the hooks have third-party dependencies. For example, to lint your
|
62 | 62 | [SCSS](http://sass-lang.com/) files, you're going to need our
|
63 |
| -[scss_lint gem](https://github.com/brigade/scss-lint). |
| 63 | +[scss_lint gem](https://github.com/sds/scss-lint). |
64 | 64 |
|
65 | 65 | Depending on the hooks you enable/disable for your repository, you'll need to
|
66 | 66 | ensure your development environment already has those dependencies installed.
|
@@ -476,7 +476,7 @@ instead of whatever contents are in your working tree (as you don't want
|
476 | 476 | unstaged changes to taint your results). Overcommit takes care
|
477 | 477 | of this for you, but to do it in a generalized way introduces this
|
478 | 478 | limitation. See the [thread tracking this
|
479 |
| -issue](https://github.com/brigade/overcommit/issues/238) for more details. |
| 479 | +issue](https://github.com/sds/overcommit/issues/238) for more details. |
480 | 480 |
|
481 | 481 | * [`*`AuthorEmail](lib/overcommit/hook/pre_commit/author_email.rb)
|
482 | 482 | * [`*`AuthorName](lib/overcommit/hook/pre_commit/author_name.rb)
|
@@ -592,9 +592,9 @@ Out of the box, `overcommit` comes with a set of hooks that enforce a variety of
|
592 | 592 | styles and lints. However, some hooks only make sense in the context of a
|
593 | 593 | specific repository.
|
594 | 594 |
|
595 |
| -At Brigade, for example, we have a number of simple checks that we run |
596 |
| -against our code to catch common errors. For example, since we use |
597 |
| -[RSpec](http://rspec.info/), we want to make sure all spec files contain the |
| 595 | +For example, you can have a number of simple checks that run |
| 596 | +against your code to catch common errors. For example, if you use |
| 597 | +[RSpec](http://rspec.info/), you can make sure all spec files contain the |
598 | 598 | line `require 'spec_helper'`.
|
599 | 599 |
|
600 | 600 | Inside our repository, we can add the file
|
@@ -704,7 +704,7 @@ ensure your thoughts, ideas, or code get merged.
|
704 | 704 | ## Community
|
705 | 705 |
|
706 | 706 | All major discussion surrounding Overcommit happens on the
|
707 |
| -[GitHub issues list](https://github.com/brigade/overcommit/issues). |
| 707 | +[GitHub issues list](https://github.com/sds/overcommit/issues). |
708 | 708 |
|
709 | 709 | You can also follow [@git_overcommit on Twitter](https://twitter.com/git_overcommit).
|
710 | 710 |
|
|
0 commit comments