-
Notifications
You must be signed in to change notification settings - Fork 9
Multiple line support for trailers and breaking change values #76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
You're right ! |
gbprod
added a commit
that referenced
this issue
Mar 13, 2025
gbprod
added a commit
that referenced
this issue
Mar 13, 2025
Should be fixed now ! |
Thank you very much for a speedy reaction! It works as expected now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to git-interpret-trailers
Documentation trailer values
can be split over multiple lines. It seems that there was support for such a
behaviour added in #49. The functionality has been dropped when added support
for overflow in #64, but I cannot find a reason for it. The overflow support
has been subsequently removed in #68, unfortunately the multiple line trailer
values has not been reinstated. Can it be added again?
While on it, I believe that breaking change values should be also allowed to
span multiple line. Although, the
BREAKING CHANGE
doesn't conform to atrailer key definition due to the whitespace(but
BREAKING-CHANGE
does!), Ibelieve that allowing multiple lines for a value will be beneficial: just the
key and a separator consume 17 characters, and an explanation may take more
than just a words (assuming: one cares about overflow).
I did a small test on my local
branch. Happy
to create a PR if that's something desireable.
The text was updated successfully, but these errors were encountered: