stylelint-problem-matcher is an action that registers a problem matcher to detect Stylelint errors in the build log and creates annotations for them.
Since this is just a problem matcher it should plug in to any existing workflow. The accompanying report formatter is needed if you're setting a custom working-directory when calling your script.
Currently it has 1 option called action which lets you add or remove the problem matcher in the event it interferes with steps farther down in the workflow.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sdras/awesome-actions/pull/316
**Author:** [@xt0rted](https://github.com/xt0rted)
**Created:** 2/3/2020
**Status:** ✅ Merged
**Merged:** 2/5/2020
**Merged by:** [@gep13](https://github.com/gep13)
**Base:** `master` ← **Head:** `patch-2`
---
### 📝 Commits (1)
- [`c30db86`](https://github.com/sdras/awesome-actions/commit/c30db861c639b97ff09349e68c27a4b835287776) Add xt0rted/stylelint-problem-matcher
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
[stylelint-problem-matcher](https://github.com/xt0rted/stylelint-problem-matcher) is an action that registers a problem matcher to detect Stylelint errors in the build log and creates annotations for them.
Since this is just a problem matcher it should plug in to any existing workflow. The accompanying [report formatter is needed](https://github.com/xt0rted/stylelint-problem-matcher#using-with-sub-folders) if you're setting a custom [`working-directory`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsrun) when calling your script.
Currently it has 1 option called `action` which lets you `add` or `remove` the problem matcher in the event it interferes with steps farther down in the workflow.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sdras/awesome-actions/pull/316
Author: @xt0rted
Created: 2/3/2020
Status: ✅ Merged
Merged: 2/5/2020
Merged by: @gep13
Base:
master← Head:patch-2📝 Commits (1)
c30db86Add xt0rted/stylelint-problem-matcher📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
stylelint-problem-matcher is an action that registers a problem matcher to detect Stylelint errors in the build log and creates annotations for them.
Since this is just a problem matcher it should plug in to any existing workflow. The accompanying report formatter is needed if you're setting a custom
working-directorywhen calling your script.Currently it has 1 option called
actionwhich lets youaddorremovethe problem matcher in the event it interferes with steps farther down in the workflow.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.