fix: trim message when exceeds maximum characters#124
Merged
mshick merged 6 commits intomshick:mainfrom Mar 12, 2026
Merged
Conversation
trim message when exceeds maximum characters
glureau
approved these changes
Sep 19, 2024
glureau
left a comment
There was a problem hiding this comment.
Thanks for your work! Note that this won't be able to properly cut the markdown syntax. (Thanksfully github should be able to handle that in most cases.)
Owner
|
@ljetten 👍 |
Owner
|
@all-contributors please add @ljetten for code |
Contributor
|
I've put up a pull request to add @ljetten! 🎉 |
This was referenced Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Partially solving #93 to at least not have the github action fail when message from path exceeds maximum characters set by GitHub.
Used kishaningithub/github-actions-expermiments#1 (comment) message to test.