feat: #3585541 Add ai_translate-specific issue and merge request templates

Christoph Breidertrequested to merge
issue/ai_translate-3585541:3585541-add-ai-translate-specific-issue-and-merge-request-templates into 2.0.x

Description

Adds the .gitlab/issue_templates/ and .gitlab/merge_request_templates/Default.md templates, adapted from the parent drupal/ai project to fit ai_translate's own scope:

  • Component label options now reflect this module's real areas (content translation, interface translation, field text extractors, provider, settings, drush) instead of drupal/ai submodule labels (aiAgent, aiApiExplorer, aiChatbot, …).
  • Added an "AI Usage" disclosure checkbox to all 5 issue templates.
  • Testing-setup snippets now include enabling content_translation/ai_translate and translating a node, not just adding a provider key.
  • feature_request.md's "Affected modules / components" example now lists this module's real areas.

Related to #3585541.

Testing instructions

No application code is changed — this MR only adds markdown template files.

  1. On this MR's target project, start a new issue and confirm each of the 5 templates (Bug report, Feature request, Plan, Support request, Task) is available in the description-template dropdown and renders correctly.
  2. Start a new merge request and confirm the "Default" template is offered and renders correctly.

Checklist

  • I have linked the related issue in the MR title or description
  • I have performed a self-review of my own code
  • I have added or updated tests, or explained in the description why this change is not covered by tests — N/A: markdown templates only, no executable code.
  • I have updated documentation for any new or changed functionality — N/A: these files are the templates themselves.
  • I have written testing instructions and verified them locally — instructions above are written; rendering in the GitLab UI still needs manual confirmation after this branch merges.
  • I have noted any required post-merge steps (config imports, cache rebuilds, manual changes) — none required.
  • This MR contains no breaking API or hook changes, or they are explicitly documented in the description

AI Compliance

Note

Check the one that best describes your usage, or leave all unchecked if AI was not significantly used.

  • AI Assisted Code
    Mainly written by a human; AI used for autocomplete or partial generation under full human supervision.

  • AI Generated Code
    Mainly generated by AI, reviewed and approved by a human before this MR was created.

  • Vibe Coded
    Generated by AI and only functionally reviewed before this MR was created.

Merge request reports