fluent/fluent-logger-python should use its own account for travis-ci.org and coveralls.io - #32
Merged
Merged
Conversation
Contributor
|
Yep, this was explained in #17 but apparently missed while merging. |
kzk
added a commit
that referenced
this pull request
May 12, 2015
fluent/fluent-logger-python should use its own account for travis-ci.org and coveralls.io
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build status badges are linked to a fork of @EvaSDK and CI and coverage calculation aren't working on fluent/fluent-logger-python. This repo should setup its own accounts on travis-ci.org and coveralls.io.