cloudposse / cloudposse/github-commenter
Message body too long?
- Dominant language
- Go
- Stars
- 112
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the Feature
If message body exceeds githubs max char limit, it fails. Would it be possible to count characters in message and split into separate comment calls if necessary.
### Expected Behavior
split messsage into separate comments/multiple comments if char limit is exceeded
### Use Case
Fails to comment on PR if message body is too long.
### Describe Ideal Solution
Split into multiple comments
### Alternatives Considered
_No response_
### Additional Context
_No response_
Contributor guide
Research direction
Start by tracing the command path that creates GitHub comments and identify where the message body is sent. The work is complete when bodies exceeding GitHub's character limit are split into multiple comments and a pull request, issue, or commit can be commented on successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100