>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue infrastructure#3592916. --> Reported by: [webchick](https://www.drupal.org/user/24967) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Paraphrasing from Slack <a href="https://drupal.slack.com/archives/CGKLP028K/p1780185330490939">https://drupal.slack.com/archives/CGKLP028K/p1780185330490939</a></p> <p>The Drupal AI project recently added <a href="https://docs.gitlab.com/user/project/description_templates/">GitLab Description Templates</a> for different types of issues (e.g. bug report, feature request) and merge requests: <a href="https://git.drupalcode.org/project/ai/-/tree/1.x/.gitlab?ref_type=heads">https://git.drupalcode.org/project/ai/-/tree/1.x/.gitlab?ref_type=heads</a></p> <p>Now, other projects in the AI ecosystem are starting to copy them (<a href="https://git.drupalcode.org/project/ai_best_practices/-/merge_requests/39">example</a> from AI Best Practices), but the problem with that is these templates all end up being "forks" of each other.</p> <p>If the "upstream" Drupal AI project makes future improvements to their issue/MR templates, we won't necessarily know about that, and their changes won't get reflected in ours without manual syncing. And now we are set up to create <strong> terrible UX</strong> for AI ecosystem contributors because when they're in AI project A the issue forms are like this but when they're in AI project B they are subtly different and given there are like 457 different AI modules (give or take ;)) this is going to spin out of control, fast. :\</p> <p><strong>Important note for AI haters</strong>: &#129315; While these templates <em>originated</em> in the Drupal AI project, these improved templates look to me to be genuinely useful to <em>any</em> project, not just AI ecosystem modules.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>I asked new smarty-pants Claude Opus 8.4 about this problem, and its recommendation was actually to set default templates at the <strong>instance</strong> level (see: <a href="https://docs.gitlab.com/administration/settings/instance_template_repository/">Instance template repository</a>) by pointing it at a project with shared governance (akin to what we do for coding standards) that sets up "reasonable defaults" for everyone, with individual projects being able to override them only when/if that makes sense.</p> <p>For example, AIBP might want to make a <code>skill.md</code> or <code>eval.md</code> file for things particular to our project, but not all Drupal projects; that's fine, and what the feature is intended to do.</p> <p>Claude even discovered we apparently <strong>already</strong> have such a thing at <a href="https://git.drupalcode.org/project/gitlab_templates">https://git.drupalcode.org/project/gitlab_templates</a> but that right now it's purely scoped for CI/CD and not issue/MR templates.</p> <p>Proposed resolution is therefore two-fold:</p> <p>1. Either expand the remit of <a href="https://git.drupalcode.org/project/gitlab_templates">https://git.drupalcode.org/project/gitlab_templates</a> or create a different "canonical" project to hold issue/MR templates (I suspect there can be only one though, based on the name of the setting).<br> 2. Populate it with the <a href="https://git.drupalcode.org/project/ai/-/tree/1.x/.gitlab?ref_type=heads">templates</a> from the Drupal AI module as a starting point.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>