Skip to content
Snippets Groups Projects
Commit dabdbda7 authored by Liam Morland's avatar Liam Morland Committed by Robert Kasza
Browse files

Issue #3522503: Enable GitLab CI automated testing

parent 4f5d5c32
No related branches found
No related tags found
1 merge request!11Issue #3522503: Enable GitLab CI automated testing
Pipeline #520938 canceled
################
# GitLabCI template for Drupal projects.
#
# This template is designed to give any Contrib maintainer everything they need to test, without requiring modification.
# It is also designed to keep up to date with Core Development automatically through the use of include files that can be centrally maintained.
# As long as you include the project, ref and three files below, any future updates added by the Drupal Association will be used in your
# pipelines automatically. However, you can modify this template if you have additional needs for your project.
# The full documentation is on https://project.pages.drupalcode.org/gitlab_templates/
################
# For information on alternative values for 'ref' see https://project.pages.drupalcode.org/gitlab_templates/info/templates-version/
# To test a Drupal 7 project, change the first include filename from .main.yml to .main-d7.yml
include:
- project: $_GITLAB_TEMPLATES_REPO
ref: $_GITLAB_TEMPLATES_REF
file:
- '/includes/include.drupalci.main.yml'
- '/includes/include.drupalci.variables.yml'
- '/includes/include.drupalci.workflows.yml'
#
################
# Pipeline configuration variables are defined with default values and descriptions in the file
# https://git.drupalcode.org/project/gitlab_templates/-/blob/main/includes/include.drupalci.variables.yml
# Uncomment the lines below if you want to override any of the variables. The following is just an example.
################
# variables:
# SKIP_ESLINT: '1'
# OPT_IN_TEST_NEXT_MAJOR: '1'
# _CURL_TEMPLATES_REF: 'main'
......@@ -45,7 +45,7 @@ For setting styles, proper CSS syntax must be used.
Setting the classes won't be enough. You need to make sure that the layout
(that you chose for the section) uses the {{ attributes }} variable in its
template for section classes and attributes and
also {{ region_attributes.REGIONNAME }} for each region classes and attributes.
also {{ region_attributes.REGION_NAME }} for each region classes and attributes.
Because that variable contains the specified classes. An example
for the variable usage is in Drupal core's layout--onecol.html.twig:
......
......@@ -7,7 +7,7 @@
"issues": "https://drupal.org/project/issues/layout_custom_section_classes",
"source": "https://cgit.drupalcode.org/layout_custom_section_classes"
},
"license": "GPL-2.0+",
"license": "GPL-2.0-or-later",
"require": {
"drupal/core": "^9.5|^10|^11",
"neilime/php-css-lint": "^3.0"
......
......@@ -411,7 +411,7 @@ function layout_custom_section_classes_help($route_name, RouteMatchInterface $ro
// https://github.com/phpmd/phpmd/issues/24
unset($route_match);
switch ($route_name) {
// Main module help for the blizz_table_field module.
// Main module help for the layout_custom_section_classes module.
case 'help.page.layout_custom_section_classes':
$text = file_get_contents(dirname(__FILE__) . '/README.md');
if (!\Drupal::moduleHandler()->moduleExists('markdown')) {
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment