Adding Labels To Pulls

## Description and Impact
> What impact does this change have for production?

## Deploy Plan
> Does Infrastructure need to know anything special about this deploy?

## Rollback Plan
* To roll back this change, revert the merge with: `git revert -m 1 MERGE_SHA` and perform another deploy.

## URLs
> Links to bug tickets or user stories.

## QA Plan
> Fill in scenarios below. Review [QA Best Practices](https://source.sportngin.com/page/show/1227795-qa-best-practices).

#### Risk Level:
- [ ] Low
- [ ] Medium
- [ ] High

#### Happy Path Scenarios
* Happy Path scenario 1
* Happy Path scenario 2

#### Additional Scenarios (Edge Case, Negative, etc.)
* Edge case scenario 1
* Edge case scenario 2

#### Regression Scenarios
* Regression item on related feature 1
* Regression item on related feature 2

Mental note check.—
Elliot Hursh 
Columbia University '13

On Thu, Jul 3, 2014 at 3:54 PM, Ian Ehlert <notifications@github.com>
wrote:

>> @@ -28,5 +29,10 @@ def self.create_or_update(github_pull)
>>          return pull if pull.update_attributes(pull_data)
>>          Rails.logger.debug pull.errors.inspect
>>        end
>> +
>> +      def add_labels(labels)
>> +        labels.map!{|v| Hubstats::Label.where(name: v.name).first}
>> +        self.labels = labels
> Maybe HABTM relations handle that automatically, I guess I can't remember. Keep an eye out for that causing problems though.
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/sportngin/hubstats/pull/21/files#r14537375