Get method for size limitation on PR content #133
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
charsLimitation is not mentioned in the docs, found references at: https://github.com/orgs/community/discussions/27190
Gitlab
1,048,576
chars docs1,000,000
chars docsBitBucket
32,768
chars:Azure Repos
4,000
charsLimitation is not mentioned in the docs, found references at: https://developercommunity.visualstudio.com/t/Raise-the-character-limit-for-pull-reque/365708?stateGroup=active
150,000
charsLimitation is not mentioned in the docs, found references at: Comment cannot be longer than 150000 characters - revisited Azure/AzOps#652