Skip to content

fix: trim message when exceeds maximum characters#124

Merged
mshick merged 6 commits intomshick:mainfrom
ljetten:main
Mar 12, 2026
Merged

fix: trim message when exceeds maximum characters#124
mshick merged 6 commits intomshick:mainfrom
ljetten:main

Conversation

@ljetten
Copy link
Copy Markdown
Contributor

@ljetten ljetten commented May 16, 2024

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.

Copy link
Copy Markdown

@glureau glureau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.)

@mshick
Copy link
Copy Markdown
Owner

mshick commented Mar 12, 2026

@ljetten 👍

@mshick mshick changed the title Trim message when exceeds maximum characters fix: trim message when exceeds maximum characters Mar 12, 2026
@mshick
Copy link
Copy Markdown
Owner

mshick commented Mar 12, 2026

@all-contributors please add @ljetten for code

@mshick mshick merged commit a62f3c4 into mshick:main Mar 12, 2026
3 of 6 checks passed
@allcontributors
Copy link
Copy Markdown
Contributor

@mshick

I've put up a pull request to add @ljetten! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants