Repository navigation
Add GitHub Actions CI/CD pipeline for o2switch deployment - #2
Closed
maximejolivet wants to merge 39 commits into
Closed
maximejolivet wants to merge 39 commits into
maximejolivet wants to merge 39 commits into
Conversation
…and build by lando
Delete local Lando override and several tailwind_starter block config sync files. This cleans up repository configuration by removing .lando.local.yml and the theme-provided block definition files (breadcrumbs, content, local_actions, messages, page_title, primary/secondary local tasks) from config/sync.
Add a new settings.local.php for environment-based local configuration (requires APP_ENV, includes DB credentials for a local drupal11 setup and sets config sync directory). Normalize PHP brace/style in tailwind_hmr LibraryHooks.php and minor library key handling whitespace/format changes. Remove tailwind_starter from core.extension.yml and update site UUID in system.site.yml. Update docker/README.md wording to English for macOS instructions and fix minor newline in base.css.
Update project README to include instructions for creating a local SSL certificate (mkcert) in web/themes/custom/tailwind/plugins/https_key, steps to clear cache and enable Vite dev (HMR) with lando, and example Vite console output. Also update the plugin README to add brew install mkcert (and nss for Firefox) and a minor newline/formatting fix for the generated cert/key file names.
Add brief notes to the README clarifying that edits to /src/css files should be visible in the IDE and that the page needs to be reloaded to pick up HMR changes. These small clarifications improve developer experience when working with the CSS and live-reload setup.
Update theme tooling: README badges updated for Vite 7.3.1 and Tailwind CSS 4.2. package.json now requires vite ^7.3.1 and bumps related devDependencies (@tailwindcss/vite, tailwindcss, prettier, prettier-plugin-tailwindcss, vite-plugin-live-reload). package-lock.json was regenerated to reflect the upgraded dependency tree (updated esbuild and rollup platform builds, new helper packages such as @jridgewell/*, and several optional platform artifacts). Run npm install or npm ci to apply the lockfile changes locally.
Update composer.json to require drupal/gin ^5.0 and add *.gz to .gitignore. composer.lock was regenerated with many dependency upgrades and metadata updates (notably drupal/core, core-recommended and core-composer-scaffold -> 11.3.3, asm89/stack-cors v2.3.0, doctrine/lexer 3.0.1, various consolidation/* and symfony package bumps, and other transitive version changes). Lockfile changes reflect resolved versions, references, timestamps, and compatibility adjustments.
Update composer.lock to bump multiple dependencies (notably drupal/core to 11.3.8, guzzlehttp/psr7, mck89/peast, many symfony components to v7.4.8, symfony polyfills to v1.36.0, and others). Apply Drupal configuration sync changes: remove admin_toolbar and system.rss config entries, remove admin_toolbar modules from core.extension, normalize empty descriptions to null, convert boolean flags to 0/1 where appropriate, change backend toolbar layout to vertical and enable sticky action buttons and favicon use_default, clear update.settings notification emails, and update various config/sync exports (views, roles, entity form modes, etc.).
Bump project frontend dependencies for compatibility and bug fixes: upgrade vite to ^8.0.9 and update devDependencies (@tailwindcss/vite, prettier, tailwindcss, vite-plugin-live-reload). Regenerate package-lock.json to capture the updated dependency tree.
Add a new .claude/CLAUDE.md bilingual (FR/EN) guide for Drupal projects. The document provides build/lint/test commands, configuration management, development and entity commands, best practices, and code style/conventions (PHP 8.3+, PSR-4, Drupal coding standards) as a contributor reference.
Regenerated composer.lock: multiple dependency version bumps and metadata updates. Notable changes include upgrades to several consolidation packages, doctrine/persistence -> 4.2.0, addition of doctrine/deprecations (1.1.6), bumped drupal/masquerade and drush/drush, laravel/prompts, league/commonmark, psy/psysh, symfony components/polyfills, and others. Also expanded Symfony compatibility ranges to include ^8 for many packages. Lockfile updated to reflect new references and timestamps after running Composer.
Add several Drupal modules and their configuration to support SEO, URL aliases and redirects, and paragraphs. composer.json updated to require metatag, pathauto, redirect, token, paragraphs, better_exposed_filters, gin_toolbar, and related modules; composer.lock refreshed. core.extension.yml enables the new modules and core configs; many config/sync files were added (metatag defaults, pathauto settings, redirect settings, redirect_404, redirect_domain, system actions, a Redirect view, admin_toolbar settings, paragraph settings, and multiple entity view modes for token/preview). Also adjust backend.settings (classic_toolbar) and add a url_redirects field to the page node form display.
Adds a CI (composer validate, phpcs, phpunit) + CD (git-pull deploy via SSH) workflow targeting o2switch shared hosting. CD triggers from a dedicated "deploy" branch rather than master, so production releases are an explicit merge/push step. settings.php now reads DB credentials from environment variables instead of hardcoded Lando values, enabling the same bootstrap file to work locally and in production. Tracks phpcs.xml so CI uses the same ruleset as local dev, and drops the unmodified settings.local.php template from version control. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maximejolivet
had a problem deploying
to
production
June 22, 2026 17:06 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 17:16 — with
GitHub Actions
Failure
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maximejolivet
had a problem deploying
to
production
June 22, 2026 17:19 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 17:26 — with
GitHub Actions
Failure
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maximejolivet
had a problem deploying
to
production
June 22, 2026 17:28 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 17:32 — with
GitHub Actions
Failure
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maximejolivet
had a problem deploying
to
production
June 22, 2026 18:08 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 18:09 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:07 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:08 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:21 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:26 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:36 — with
GitHub Actions
Failure
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:41 — with
GitHub Actions
Failure
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maximejolivet
had a problem deploying
to
production
June 22, 2026 19:52 — with
GitHub Actions
Failure
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a CI (composer validate, phpcs, phpunit) + CD (git-pull deploy via SSH) workflow targeting o2switch shared hosting. CD triggers from a dedicated "deploy" branch rather than master, so production releases are an explicit merge/push step. settings.php now reads DB credentials from environment variables instead of hardcoded Lando values, enabling the same bootstrap file to work locally and in production. Tracks phpcs.xml so CI uses the same ruleset as local dev, and drops the unmodified settings.local.php template from version control.