Skip to content

Conversation

@caniszczyk
Copy link
Contributor

@caniszczyk caniszczyk self-assigned this Oct 14, 2016
@wking
Copy link
Contributor

wking commented Oct 15, 2016

I don't know what's going on with the Travis failure; it seems like
$TRAVIS_COMMIT_RANGE is unset 1. Travis has had problems with that
in the past (travis-ci/travis-ci#1719), but they claim to have fixed
them. Maybe we just need to kick the tests?

c71bd20 looks good to me.

@Mashimiao
Copy link

@caniszczyk Do you really want to create a new branch of this project?
I think you should create branch on you own fork and create PR with that branch, not like this.

@liangchenye
Copy link
Member

@Mashimiao I guess you miss read the branch.

@Mashimiao
Copy link

No, I think I didn't. A new branch add-go-report-card has been created and pushed to this project.

@liangchenye
Copy link
Member

Oh yes, @Mashimiao I did not notice this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants