We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description: The matcher ^\s*(.+\.go):(?:(\d+):(\d+):)? (.*) is way too broad (see regex101).
^\s*(.+\.go):(?:(\d+):(\d+):)? (.*)
We are using go-generate-fast which outputs the results at the end of a go generate command as follows:
options.go: echo hello! (generated, noplugin, 2ms)
This gets caught by the matcher.
Action version: latest
Platform:
Runner type:
Tools version:
Repro steps: A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior: It should not be matching non-errors that start with filename.go:
filename.go:
Actual behavior: It is matching non-errors that start with filename.go:
It would be great to be able to disable the matchers in some way.
The text was updated successfully, but these errors were encountered:
Hello @hoshsadiq, Thank you for creating this issue and we will look into it :)
Sorry, something went wrong.
aparnajyothi-y
No branches or pull requests
Description:
The matcher
^\s*(.+\.go):(?:(\d+):(\d+):)? (.*)
is way too broad (see regex101).We are using go-generate-fast which outputs the results at the end of a go generate command as follows:
This gets caught by the matcher.
Action version:
latest
Platform:
Runner type:
Tools version:
Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior:
It should not be matching non-errors that start with
filename.go:
Actual behavior:
It is matching non-errors that start with
filename.go:
It would be great to be able to disable the matchers in some way.
The text was updated successfully, but these errors were encountered: