Skip to content

Include commit message templates when forking project

Nejc Habjan requested to merge siemens/gitlab:feat/transfer-commit-messages-to-forks into master

What does this MR do and why?

Closes Settings for default merge messages are not tra... (#354470 - closed).

Many projects will have commit message guidelines that may be enforced via CI jobs and linters. Since the CI config is preserved on forking, this may cause the default commit message templates to fail CI pipelines/not work out-of-the-box after a project has been forked. This preserves the commit message templates so that CI config that expects them will succeed by default when applied, even when MRs are targeting the fork itself.

(Suggestions: use template from target project i... (!82657 - merged) addressed part of the problem, with commit message suggestions when MRs target the source project, but this is not always the case.)

🛠 with ❤ at Siemens

/cc @bufferoverflow

Screenshots or screen recordings

Fork settings should look the same as the source e.g.:

image

How to set up and validate locally

  1. Using GDK, checkout to this branch
  2. gdk start
  3. Choose a pre-seeded project, e.g. flightjs/Flight and change default message templates under Settings > General > Merge Requests
  4. Fork Flight project to another namespace
  5. Go to forked project and check that Settings > General > Merge Requests preserved original message templates.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Nejc Habjan

Merge request reports