Skip to content

Conversation

@mfrederickson
Copy link
Contributor

Working towards errbit/errbit#371, but I need help writing the test for the close_issue method...

@mfrederickson
Copy link
Contributor Author

To test this, you'll need the Gemfile entry for errbit_plugin to point to the git repo, the close-issue branch, or point it to your local copy of that branch.

@mfrederickson
Copy link
Contributor Author

@stevecrozz I'm not sure how to make travis's ruby 2.3 test environment happy regarding this:
image
Seen here: https://travis-ci.org/errbit/errbit_github_plugin/jobs/110716111

@stevecrozz
Copy link
Member

For some reason, it has to be '2.3.0' I'm not sure why its inconsistent, but that's what works in the other repos. Btw. I just released v0.6.0 of errbit_plugin which includes your close_issue updates.

@stevecrozz
Copy link
Member

@mfrederickson Does that help clear up the build error? Probably we should get this merged and publish a new version before merging the errbit changes.

@mfrederickson
Copy link
Contributor Author

@stevecrozz looks like it worked. Thanks.

stevecrozz added a commit that referenced this pull request Mar 11, 2016
@stevecrozz stevecrozz merged commit 4945242 into errbit:master Mar 11, 2016
@mfrederickson mfrederickson deleted the github-close-issue branch March 15, 2016 16:27
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.

2 participants