Skip to content

Milestone 0.2.16 #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Apr 3, 2017
Merged

Milestone 0.2.16 #215

merged 8 commits into from
Apr 3, 2017

Conversation

Scrum
Copy link
Member

@Scrum Scrum commented Apr 3, 2017

No description provided.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 8f4e844 on milestone-0.2.16 into ** on master**.

3 similar comments
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 8f4e844 on milestone-0.2.16 into ** on master**.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 8f4e844 on milestone-0.2.16 into ** on master**.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 8f4e844 on milestone-0.2.16 into ** on master**.

@coveralls
Copy link

coveralls commented Apr 3, 2017

Coverage Status

Changes Unknown when pulling 4676e0e on milestone-0.2.16 into ** on master**.

1 similar comment
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 4676e0e on milestone-0.2.16 into ** on master**.

@Scrum Scrum merged commit e016c25 into master Apr 3, 2017
@Scrum Scrum deleted the milestone-0.2.16 branch April 3, 2017 13:05
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.

3 participants