>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3568048. --> Reported by: [littlepixiez](https://www.drupal.org/user/2568718) >>> <h3>Problem/Motivation</h3> <p>Create or contribute to DrupalForge's browser extension (<a href="https://www.drupal.org/project/drupalforge_browser_extension">https://www.drupal.org/project/drupalforge_browser_extension</a>) to add AI module testing support:</p> <p><strong>Automatic issue detection:</strong></p> <ul> <li>When visiting a drupal.org issue page, extension automatically detects: <ul> <li>Project/module name</li> <li>Issue number (for fork parameter)</li> <li>Branch name from merge requests</li> </ul> </li> </ul> <p><strong>Configuration UI:</strong></p> <ul> <li>Template selection: CMS or Core (default: CMS)</li> <li>Drupal version: 10.x, 11.x, or specific version (default: latest stable)</li> <li>AI base version: auto-detect or specify manually (default: auto-detect)</li> <li>PHP version: 8.2 or 8.3 (future enhancement)</li> </ul> <p><strong>One-click launch:</strong></p> <ul> <li>"Test this issue" button constructs DrupalForge URL with all parameters</li> <li>Opens new tab with configured testing environment</li> <li>Saves common configurations for quick reuse</li> </ul> <p><strong>Implementation approach:</strong></p> <ul> <li>Option 1: Fork DrupalForge Chrome extension and add AI-specific features</li> <li>Option 2: Contribute AI module support directly to DrupalForge extension (a lot may be irrelevant)</li> </ul> <h3>Remaining tasks</h3> <ul> <li>[x] Contact DrupalForge team about contributing vs forking</li> <li>[x] Review existing extension code and architecture</li> <li>[x] Implement issue page detection (module name, issue number, branch)</li> <li>[x] Add configuration UI (template, Drupal version, AI version)</li> <li>[x] Implement URL construction with all parameters</li> <p><del> <li>[x] Add "Test this issue" button to drupal.org issue pages</li> <p></p></del> - different approach</p> <li>[ ] Test with various AI ecosystem modules and issues</li> <li>[ ] Document extension usage</li> <li>[x] Publish extension (Chrome Web Store or internal distribution [if new extension])</li> <p><del> <li>[ ] Future: Add PHP version selection</li> <p></p></del> - out of scope here </p></ul> <h3>User workflow (after implementation)</h3> <ol> <li>Visit drupal.org issue page (e.g., ai_search issue with MR)</li> <li>Chrome extension icon shows "Test available"</li> <li>Click extension &rarr; see auto-detected values: <ul> <li>Test module: ai_search</li> <li>Issue fork: 3526789</li> <li>Branch: 123-fix-search</li> <li>AI version: auto-detect (from ai_search dependencies)</li> <li>Template: CMS (can change to Core)</li> <li>Drupal version: latest stable</li> </ul> </li> <li>Adjust any values if needed</li> <li>Click "Launch Test Environment"</li> <li>New tab opens with fully configured DrupalForge environment</li> </ol>