Skip to content
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

How to turn off problem matcher? #72

Closed
azu opened this issue Oct 20, 2019 · 2 comments
Closed

How to turn off problem matcher? #72

azu opened this issue Oct 20, 2019 · 2 comments

Comments

@azu
Copy link

azu commented Oct 20, 2019

Hi, I want to disable problem matcher like eslint-stylish.json.

console.log(`##[add-matcher]${path.join(matchersPath, 'tsc.json')}`);
console.log(
`##[add-matcher]${path.join(matchersPath, 'eslint-stylish.json')}`
);
console.log(
`##[add-matcher]${path.join(matchersPath, 'eslint-compact.json')}`
);

Because, I've created textlint that is similar with ESLint and It support same format with eslint-stylish.

I've noticed that output formatted log in GitHub Actions, problem matcher report it as error.
But, It is just console log for testing and it is not actual error.

image

https://github.com/textlint/textlint/runs/267131582

Is there any chance setup-node provide an option to disable problem matcher?

Related

azu added a commit to textlint/textlint that referenced this issue Oct 20, 2019
@xt0rted
Copy link

xt0rted commented Dec 23, 2019

Try writing out ::remove-matcher owner=eslint-compact:: in a step after actions/setup-node (from the docs). If you're adding your own problem matchers then you can use the same names as these and the last ones registered will take priority.

@azu
Copy link
Author

azu commented Dec 26, 2019

Thanks!

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

No branches or pull requests

2 participants