[x] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] I used go fmt ./... for formatting the code before submitting the pull request.
[x] This feature is included on all supported VCS providers - GitHub, Bitbucket cloud, Bitbucket server, GitLab and Azure Repos.
[x] I added the relevant documentation for the new feature.
Add new methods to get the size limitations for the pull request content (details/comments).
It allows us to figure out dynamically if the content will overflow and the API will result in failures.
11:07:00 [Error] couldn't add pull request comment: Status: 400 Bad Request, Body: {"errors":[{"context":"text","message":"Please enter a non-empty value less than 32768 characters","exceptionName":null}]}
[![👍 Frogbot scanned this pull request and found that it did not add vulnerable dependencies.](https://raw.githubusercontent.com/jfrog/frogbot/master/resources/v2/noVulnerabilityBannerPR.png)](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)
go fmt ./...
for formatting the code before submitting the pull request.Add new methods to get the size limitations for the pull request content (details/comments). It allows us to figure out dynamically if the content will overflow and the API will result in failures.
Limitations found:
Github
65,536
chars Limitation is not mentioned in the docs, found references at: https://github.com/orgs/community/discussions/27190Gitlab
1,048,576
chars docs1,000,000
chars docsBitBucket
32,768
chars:Azure Repos
4,000
chars Limitation is not mentioned in the docs, found references at: https://developercommunity.visualstudio.com/t/Raise-the-character-limit-for-pull-reque/365708?stateGroup=active150,000
chars Limitation is not mentioned in the docs, found references at: https://github.com/Azure/AzOps/issues/652