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.

Sign up for GitHub

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

Jump to bottom

testing eslint standard config #3

Merged

ovhemert merged 1 commit into master from codacy-test

Jan 14, 2019

Owner

ovhemert commented Jan 14, 2019

No description provided.


          testing eslint standard config

9a5c8d9

ovhemert merged commit 9a5c8d9 into master

coveralls commented Jan 14, 2019

Pull Request Test Coverage Report for Build 31

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals
Change from base Build 27:	0.0%
Covered Lines:	72
Relevant Lines:	72

💛 - Coveralls

3 similar comments

coveralls commented Jan 14, 2019

Pull Request Test Coverage Report for Build 31

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals
Change from base Build 27:	0.0%
Covered Lines:	72
Relevant Lines:	72

💛 - Coveralls

coveralls commented Jan 14, 2019

Pull Request Test Coverage Report for Build 31

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals
Change from base Build 27:	0.0%
Covered Lines:	72
Relevant Lines:	72

💛 - Coveralls

coveralls commented Jan 14, 2019

Pull Request Test Coverage Report for Build 31

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals
Change from base Build 27:	0.0%
Covered Lines:	72
Relevant Lines:	72

💛 - Coveralls

ovhemert deleted the codacy-test branch

January 14, 2019 20:55

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