Skip to content

creating the GitHub comment fails if package has too many failing lints #55

@paulstaab

Description

@paulstaab

I tried to enable lintr on travis in a package that has a lot of failing lints. It seems that the creation of the GitHub comment fails because it would be too long:

$ Rscript -e 'lintr::lint_package()'
Error in stop(httr::http_condition(response, "error", message = httr::content(response, :
{
"message": "Validation Failed",
"errors": [
{
"resource": "CommitComment",
"code": "custom",
"field": "body",
"message": "body is too long (maximum is 65535 characters)"
}
],
"documentation_url": "https://developer.github.com/v3/repos/comments/#create-a-commit-comment"
}
Calls: print -> print.lints -> github_comment
Execution halted

I guess just printing the first 50 to 100 lints would be sufficient in that case...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions