Permalink
Browse files

Remove files and add moved notice

  • Loading branch information...
1 parent 773395a commit db19286b31a082e9ee2c2c11d63aed84a2ed8f7b @stevenharman stevenharman committed Dec 28, 2012
View
@@ -1,20 +0,0 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-tags
-.rvmrc
-.rbenv-version
View
4 .rspec
@@ -1,4 +0,0 @@
---colour
--I spec/support
--r rspec-spies
--r pry
View
@@ -1,5 +0,0 @@
-language: ruby
-rvm:
- - 1.8.7
- - 1.9.2
- - 1.9.3
View
@@ -1,62 +0,0 @@
-### dev
-[full changelog](https://github.com/highgroove/git_tracker/compare/v1.3.0...master)
-Enhancements
-
-* Support Ruby 1.8.7
-* Generate standalone binary via `rake git-tracker`
-
-### 1.3.1 / 2012-04-23
-[full changelog](https://github.com/highgroove/git_tracker/compare/v1.3.0...v1.3.1)
-
-Bug fixes
-
-* Bring back fourth Pivotal Tracker keyword, `delivered`
-
-### 1.3.0 / 2012-04-23
-[full changelog](https://github.com/highgroove/git_tracker/compare/v1.2.0...v1.3.0)
-
-Enhancements
-
-* Allow all three Pivotal Tracker keyword states: `fixed`, `completed`, and `finished`
-
-Bug fixes
-
-* Pivotal Tracker keywords are case-insensitive
-
-### 1.2.0 / 2012-04-21
-[full changelog](https://github.com/highgroove/git_tracker/compare/v1.1.0...v1.2.0)
-
-Enhancements
-
-* Allow Pivotal Tracker keyword states: `Delivers` and `Fixes` [KensoDev](https://github.com/KensoDev)
-
-Bug fixes
-
-* Exit with non-zero status code when a commit exists [issue
- #3](https://github.com/highgroove/git_tracker/issues/3)
-* Exit with non-zero status code with not in a Git repository
-
-### 1.1.0 / 2012-04-03
-[full changelog](https://github.com/highgroove/git_tracker/compare/v1.0.0...v1.1.0)
-
-Enhancements
-
-* The hash preceding the story number is optional [CraigWilliams](https://github.com/CraigWilliams)
-
-Bug fixes
-
-* Fix case-sensitivity issue w/English library
-* Exit with non-zero status code with not in a Git repository [issue
- #1](https://github.com/highgroove/git_tracker/issues/1)
-
-### 1.0.0 / 2012-03-31
-[full changelog](https://github.com/highgroove/git_tracker/compare/v0.0.1...v1.0.0)
-
-Enhancements
-
-* Hook can install itself in a Git repository
-
-### 0.0.1 / 2012-03-23
-[full changelog](https://github.com/highgroove/git_tracker/compare/5fbbe061e721c1f86fdd5d78a4bfb4c61a0eaf5c...v0.0.1)
-
-* Initial release
View
@@ -1,4 +0,0 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in git_tracker.gemspec
-gemspec
View
22 LICENSE
@@ -1,22 +0,0 @@
-Copyright (c) 2012 Steven Harman
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
View
158 README.md
@@ -1,157 +1,3 @@
-# GitTracker
+:warning: This project has a new home!
-[![Build Status](https://secure.travis-ci.org/highgroove/git_tracker.png)](http://travis-ci.org/highgroove/git_tracker)
-[![Dependency Status](https://gemnasium.com/highgroove/git_tracker.png)](https://gemnasium.com/highgroove/git_tracker)
-
-*GitTracker*, or *git-tracker*, is a Git hook that will scan your current
-branch name looking for something it recognizes as a [Pivotal Tracker][pt]
-story number. If it finds one, it will automagically add it, in the [special
-format][pt-format], to your commit message.
-
-## Installation
-
-You need to get the `git-tracker` executable on your system.
-
-### RubyGems
-
-Currently, this is the only option, but I plan to have a standalone version
-ready soon.
-
-```bash
-$ gem install git_tracker
-```
-
-Once you have the `git-tracker` executable on your system you need to install
-the hook into your local Git repository.
-
-```bash
-# from inside a local Git repository
-$ git-tracker install
-```
-
-This will put the `prepare-commit-msg` hook in the `/path/to/repo/.git/hooks`
-directory and make it executable.
-
-**NOTE:** The hook needs to be installed just once for each repository in which
-you will use it.
-
-## Usage
-
-With the hook installed in a repository, create branches being sure to include
-the Pivotal Tracker story number in the branch name.
-
-```bash
-$ git checkout -b a_useful_and_helpful_name_8675309
-```
-
-When you commit, Git will fire the hook which will find the story number in the
-branch name and prepare your commit message so that it include the story number
-in the special Pivotal Tracker syntax.
-
-```bash
-# on branch named `best_feature_ever-8675309`
-$ git commit
-```
-
-Will result in a commit message something like: *(notice the two empty lines at
-the top)*
-
-```diff
-
-
-[#8675309]
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# On branch best_feature_ever-8675309
-# Changes to be committed:
-# (use "git reset HEAD <file>..." to unstage)
-#
-# new file: feature.rb
-#
-
-```
-
-You should then add a [useful and responsible commit message][tpope]. :heart:
-
-### Passing commit messages via command line
-
-If you pass a commit message on the command line the hook will still add the
-story number, preceded by an empty line, to the end of your message.
-
-```bash
-# on branch named `best_feature_ever-8675309`
-$ git commit -m'Look at this rad code, yo!'
-```
-
-Results in this commit message:
-
-```
-Look at this rad code, yo!
-
-[#8675309]
-```
-
-However, if you include the story number in the Pivotal Tracker format in your
-commit message, the hook will do nothing.
-
-```bash
-# on branch named `best_feature_ever-8675309`
-$ git commit -m'[#8675309] Look at this rad code, yo!'
-```
-
-Results in this commit message:
-
-
-```
-[#8675309] Look at this rad code, yo!
-```
-
-### Keywords
-You can use the custom keywords that Pivotal Tracker provide with the API.
-
-The keywords are `fixed`, `completed`, `finshed`, and `delivered` in square
-brackets. You may also use different cases forms of these verbs, such as `Fix`
-or `FIXES`.
-
-If you use those keywords in your commit message, the keyword will be prepended
-to the story ID in the commit message.
-
-For example:
-
-```bash
-# on branch named `bug/redis_connection_not_initializing_8675309`
-$ git commit -am "Change the redis connection string [Fixes]"
-```
-
-Results in this commit message:
-
-```bash
-Change the redis connection string [Fixes]
-
-[Fixes #8675309]
-```
-
-### Valid branch names
-
-*git_tracker* allows you to include the story number any where in the branch
-name, optionally prefixing it with a hash (`#`). Examples:
-
- - `best_feature_ever_#8675309`
- - `best_feature_ever_8675309`
- - `8675309_best_feature_ever`
- - `#8675309_best_feature_ever`
- - `your_name/8675309_best_feature_ever`
- - `your_name/#8675309_best_feature_ever`
-
-## Contributing :octocat:
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
-
-
-[pt]: https://www.pivotaltracker.com/
-[pt-format]: https://www.pivotaltracker.com/help/api?version=v3#scm_post_commit_message_syntax
-[tpope]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+https://github.com/stevenharman/git_tracker
View
@@ -1,12 +0,0 @@
-#!/usr/bin/env rake
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-task :default => :spec
-
-file 'git-tracker' => FileList.new('lib/git_tracker.rb, lib/git_tracker/*.rb') do |task|
- $LOAD_PATH.unshift File.expand_path('../lib', __FILE__)
- require 'git_tracker/standalone'
- GitTracker::Standalone.save(task.name)
-end
View
@@ -1,4 +0,0 @@
-#!/usr/bin/env ruby
-
-require 'git_tracker'
-GitTracker::Runner.execute(*ARGV)
View
@@ -1,26 +0,0 @@
-# -*- encoding: utf-8 -*-
-require File.expand_path('../lib/git_tracker/version', __FILE__)
-
-Gem::Specification.new do |gem|
- gem.name = "git_tracker"
- gem.version = GitTracker::VERSION
- gem.authors = ["Steven Harman"]
- gem.email = ["steveharman@gmail.com"]
- gem.homepage = "https://github.com/highgroove/git_tracker"
- gem.summary = %q{Teaching Git about Pivotal Tracker.}
- gem.description = <<-EOF
- Some simple tricks that make working with Pivotal Tracker even
- better... and easier... um, besier!
- EOF
-
- gem.add_development_dependency "rspec", "~> 2.9"
- gem.add_development_dependency "rspec-spies", "~> 2.0"
- gem.add_development_dependency "pry", "~> 0.9"
- gem.add_development_dependency "activesupport", "~> 3.2"
- gem.add_development_dependency "rake"
-
- gem.files = `git ls-files`.split("\n")
- gem.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
- gem.executables = %w(git-tracker)
- gem.require_paths = ["lib"]
-end
View
@@ -1,8 +0,0 @@
-require 'git_tracker/hook'
-require 'git_tracker/repository'
-require 'git_tracker/prepare_commit_message'
-require 'git_tracker/runner'
-require 'git_tracker/branch'
-require 'git_tracker/commit_message'
-require 'git_tracker/version'
-
View
@@ -1,24 +0,0 @@
-require 'English'
-require 'git_tracker/repository'
-
-module GitTracker
- module Branch
- def self.story_number
- current[/#?(\d+)/, 1]
- end
-
- def self.current
- branch_path = `git symbolic-ref HEAD`
-
- Repository.ensure_exists unless exit_successful?
-
- branch_path[%r{refs/heads/(.+)}, 1] || ''
- end
-
- private
-
- def self.exit_successful?
- $CHILD_STATUS.exitstatus == 0
- end
- end
-end
Oops, something went wrong.

0 comments on commit db19286

Please sign in to comment.