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
Describe the bug I noticed that pr-compliance-action did not flag the PR description in open-sauced/open-sauced#1299 Looking back, my suspicion is because the PR template markdown includes HTML comments that instruct the contributor how to refer to an issue (https://raw.githubusercontent.com/open-sauced/.github/main/.github/PULL_REQUEST_TEMPLATE.md). The action is picking this instruction up as a false positive.
pr-compliance-action
To Reproduce Steps to reproduce the behavior: Submit a PR to open-sauced with an invalid PR body while leaving the commented instructions intact.
Workflow File Contents See those in open-sauced
Expected behavior Action flags for invalid PR description
Screenshots N/A
Additional context N/A
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
I noticed that
pr-compliance-action
did not flag the PR description in open-sauced/open-sauced#1299Looking back, my suspicion is because the PR template markdown includes HTML comments that instruct the contributor how to refer to an issue (https://raw.githubusercontent.com/open-sauced/.github/main/.github/PULL_REQUEST_TEMPLATE.md). The action is picking this instruction up as a false positive.
To Reproduce
Steps to reproduce the behavior:
Submit a PR to open-sauced with an invalid PR body while leaving the commented instructions intact.
Workflow File Contents
See those in open-sauced
Expected behavior
Action flags for invalid PR description
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: