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
Currently pouch project uses circleci to check the markdown file validation. If it fails, we need to tell users where to check the rule.
So if circleci fails, it should throw errors to webhook receiver(pouchrobot), and dear robot would attach a comment to the pull request.
When attaching a comment to pr, we should aggregate the error into a single one since travisCI would fail as well.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently pouch project uses circleci to check the markdown file validation. If it fails, we need to tell users where to check the rule.
So if circleci fails, it should throw errors to webhook receiver(pouchrobot), and dear robot would attach a comment to the pull request.
When attaching a comment to pr, we should aggregate the error into a single one since travisCI would fail as well.
The text was updated successfully, but these errors were encountered: