- Issue created by @mark_fullmer
- Status changed to Fixed
10 months ago 5:11pm 26 February 2024 Automatically closed - issue fixed for 2 weeks with no activity.
Gitlab CI is now generally available for testing contributed module code. See https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →
1. Add GitLab CI configuration for this project:
A. Go to https://git.drupalcode.org/project/google_cse and sign in.
B. Use the repository UI (not the Web IDE) to add a new file (+ icon).
C. Type the file name as .gitlab-ci.yml
D. You will be presented with the option to select a template, select the Drupal Association's template.gitlab-ci.yml from the top of the list.
E. Use the UI to complete the commit to the repository (i.e., do not create a merge request, etc.)
F. Confirm successful integration at https://git.drupalcode.org/project/google_cse/-/pipelines
2. From this module's "Automated Testing" tab, click "Edit" for the existing Drupal CI test, then "Remove"
3. From this module's "Edit" tab, click the "Issues" tab and populate the "Custom issue summary template" with the following:
<h3 id="summary-problem-motivation">Problem/motivation</h3>
<h3 id="summary-steps-reproduce">Steps to reproduce</h3>
<ol>
<li>Go to...</li>
<li>Click on...</li>
<li>Observe [describe the expected and actual output]</li>
</ol>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<div class="note-warning">This module uses Gitlab CI for automated testing of proposed code changes. To contribute code changes, create a merge request. Patch files will not trigger automated testing and are not sufficient for review.</div>
Fixed
4.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.