You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1b08f15
Browse filesBrowse the repository at this point in the historyBrowse files
fix(docs-issue-picker): require project-qualified issue input, support GitLab issue URLs
Drupal issue IDs are no longer globally unique now that drupal.org issue
queues are migrating to GitLab per-project (#163) - a bare
number can silently resolve to the wrong project. Drop bare-number input,
add GitLab issue URL parsing, and fall back to the GitLab Issues API when
a drupal.org issue lookup comes back empty because the project migrated.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/drupal-issue.html
+97-52Lines changed: 97 additions & 52 deletions
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@
21
21
<!-- id="main-content" is the skip link target (WCAG 2.4.1) -->
22
22
<divclass="cds-page" id="main-content">
23
23
<h1>Drupal Issue Picker</h1>
24
-
<pclass="cds-page__subtitle">Paste a drupal.org core or contrib issue URL or number, or a contrib project URL or machine name. We load issue metadata and fork branches when applicable.</p>
24
+
<pclass="cds-page__subtitle">Paste a drupal.org or GitLab core/contrib issue URL, or a contrib project URL or machine name. We load issue metadata and fork branches when applicable.</p>
25
25
26
26
<divclass="cds-note cds-note--intro">
27
27
To create a clean Drupal core environment without contrib modules or issue forks, try the <aclass="cds-link" href="drupal-core">Guided Drupal core</a> form.
@@ -31,9 +31,9 @@ <h1>Drupal Issue Picker</h1>
31
31
<!-- Explicit <label> associates the field name with the input for screen readers.
32
32
Visually hidden because the heading and subtitle already describe the field.
33
33
WCAG 1.3.1 Info and Relationships / 3.3.2 Labels or Instructions (Level A) -->
34
-
<labelfor="issue-input" class="cds-sr-only">Issue number, URL, or project name</label>
34
+
<labelfor="issue-input" class="cds-sr-only">Issue URL or project name</label>
'No issue fork exists for #'+nid+' on '+projectName+' yet. Visit the issue page on drupal.org and click "Get push access" to create a fork, then come back here.',
798
+
'No issue fork exists for #'+nid+' on '+projectName+' yet. Visit the issue page and click "Get push access" to create a fork, then come back here.',
756
799
'info'
757
800
);
758
801
}else{
759
802
setStatus(
760
-
'No issue fork exists for #'+nid+' yet. To work on this issue, visit the issue page on drupal.org and click "Get push access" to create a fork, then come back here.',
803
+
'No issue fork exists for #'+nid+' yet. To work on this issue, visit the issue page and click "Get push access" to create a fork, then come back here.',
761
804
'info'
762
805
);
763
806
}
@@ -766,22 +809,24 @@ <h2 id="feedback">Feedback & Community</h2>
766
809
if(!branchResp.ok)thrownewError('git.drupalcode.org API returned '+branchResp.status);
767
810
constbranches=awaitbranchResp.json();
768
811
769
-
// Step 3: try to get visible branches from Drupal.org issue page (drupalorgBranchData)
0 commit comments