suggest allow custom default merge message template #5243

Closed
opened 2025-11-02 06:18:59 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @a1012112796 on GitHub (Apr 16, 2020).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Hello, I think it's usefull , if user can define merge message template, maybe we can allow user to do it by define .gitea/MERGE_MESSAGE_{merge_style}_TEMPLATE.md file in base branch. which is Similar to issue and pr template. thanks.

Screenshots

Originally created by @a1012112796 on GitHub (Apr 16, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description Hello, I think it's usefull , if user can define merge message template, maybe we can allow user to do it by define ``.gitea/MERGE_MESSAGE_{merge_style}_TEMPLATE.md`` file in base branch. which is Similar to issue and pr template. thanks. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
Author
Owner

@stale[bot] commented on GitHub (Jun 15, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 15, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@zeripath commented on GitHub (Jun 15, 2020):

I think this is still valid

@zeripath commented on GitHub (Jun 15, 2020): I think this is still valid
Author
Owner

@zeripath commented on GitHub (Sep 30, 2020):

A relatively simple first solution would be to just provide per-instance templates - these could actually use gotemplates and have the models.Issue etc. passed in.

Per-repository templates would need to go into the .gitea/ folder on the $master branch using code from the issue templates and template repositories code. If we use gotemplates for this we cannot just pass in the models.Issue etc as it would not be too difficult to use methods on the Issue to then change the User etc. Therefore some kind of defined variable replacement would be needed - Again similar to that used in issue/repository templates.

@zeripath commented on GitHub (Sep 30, 2020): A relatively simple first solution would be to just provide per-instance templates - these could actually use gotemplates and have the models.Issue etc. passed in. Per-repository templates would need to go into the .gitea/ folder on the $master branch using code from the issue templates and template repositories code. If we use gotemplates for this we cannot just pass in the models.Issue etc as it would not be too difficult to use methods on the Issue to then change the User etc. Therefore some kind of defined variable replacement would be needed - Again similar to that used in issue/repository templates.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5243