actions
/
toolkit
mirror of https://github.com/actions/toolkit
1
0
Fork 0
Code

Add another likely reason for problem matcher patterns failing 

Input lines are passed as-is to the regular expressions used by problem matcher patterns. This can lead to unexpected failures when trying to, for example, match colored terminal output, which relies on [ANSI escape sequences](https://en.wikipedia.org/wiki/ANSI_escape_code). The cause is not that obvious at a first glance because such characters are stripped from the GitHub log UI, and I think that it should be documented.
pull/1203/head
Alejandro González 2022-10-11 17:05:54 +02:00 committed by GitHub
parent 4fbc5c941a
commit 75b96d08b0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/problem-matchers.md
View File

@ -142,6 +142,8 @@ Some of the starter actions are already using problem matchers, for example:
Use ECMAScript regular expression syntax when testing patterns. Use ECMAScript regular expression syntax when testing patterns.
The patterns match the input lines as-is, without stripping ANSI escape codes or other extraneous characters. If the subject strings can contain such characters, the regular expression must account for them.
### File property getting dropped ### File property getting dropped
[Enable debug logging](https://docs.github.com/en/actions/managing-workflow-runs/enabling-debug-logging) to determine why the file is getting dropped. [Enable debug logging](https://docs.github.com/en/actions/managing-workflow-runs/enabling-debug-logging) to determine why the file is getting dropped.