-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The entire Merge template is used as the PR merge title #21435
Labels
Comments
Relevant PR #18177 |
+1. I also tried to have multiline template like
, so the first line would go to the title of merge-commit and the second to its description - but instead got I would also like to mention, that even though https://docs.gitea.io/en-us/merge-message-templates/ and #18177 mention variable |
lafriks
pushed a commit
that referenced
this issue
Dec 29, 2022
Fix #21435. Use the first line of the template as the git commit message title, and the rest as the description. ## Snapshots <img width="806" alt="image" src="https://user-images.githubusercontent.com/9418365/209644083-5d85179c-cf58-404f-bc98-c662398a2411.png"> <img width="860" alt="image" src="https://user-images.githubusercontent.com/9418365/209644392-22573090-e2c1-458b-ba44-855b79735632.png"> <img width="1154" alt="image" src="https://user-images.githubusercontent.com/9418365/209644457-a1b2711a-6787-45b4-b52c-a88d7fc132d7.png"> Co-authored-by: delvh <dev.lh@web.de>
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Description
I would like to use a merge template like so:
My expectation was that the first line is used as the title and the rest would be put in the PR message field, but it's not the case.
Instead the entire template is stripped of newline chars and jammed into the title field. See screenshot.
Gitea Version
1.17.2
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
No response
Operating System
Ubuntu 20.04
How are you running Gitea?
Official Docker image
Database
No response
The text was updated successfully, but these errors were encountered: