Skip to content

Commit 9cfb160

Browse files
authored
troubleshooting problem matchers (#341)
1 parent 2dcdf04 commit 9cfb160

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

docs/problem-matchers.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,3 +115,26 @@ Some of the starter actions are already using problem matchers, for example:
115115
- [setup-python](https://github.com/actions/setup-python/tree/master/.github)
116116
- [setup-go](https://github.com/actions/setup-go/tree/master/.github)
117117
- [setup-dotnet](https://github.com/actions/setup-dotnet/tree/master/.github)
118+
119+
## Troubleshooting
120+
121+
### Regular expression not matching
122+
123+
Use ECMAScript regular expression syntax when testing patterns.
124+
125+
### File property getting dropped
126+
127+
[Enable debug logging](https://help.github.com/en/actions/configuring-and-managing-workflows/managing-a-workflow-run#enabling-debug-logging) to determine why the file is getting dropped.
128+
129+
This usually happens when the file does not exist or is not under the workflow repo.
130+
131+
### Adding from a Docker container action
132+
133+
The matcher config file must first be copied to a volume that is accessible from the runner.
134+
135+
For example:
136+
137+
```sh
138+
cp /eslint-compact.json "$HOME/"
139+
echo "::add-matcher::$HOME/eslint-compact.json
140+
```

0 commit comments

Comments
 (0)