Skip to content

Conversation

@AlexSkrypnyk
Copy link
Member

@AlexSkrypnyk AlexSkrypnyk commented Sep 29, 2025

Closes #2023

Summary by CodeRabbit

  • Chores
    • Enhanced CI/CD to support releases triggered by tags in addition to branch pushes.
    • Expanded branch coverage (including master, develop, and project-specific patterns) for automated workflows.
    • Introduced a deployment mode indicator to differentiate tag-based versus branch-based deployments, improving release flow clarity.
    • No changes to application functionality; end-user experience remains unchanged.

@coderabbitai
Copy link

coderabbitai bot commented Sep 29, 2025

Walkthrough

Adds tag triggers to the GitHub Actions workflow, expands branch patterns, and sets a VORTEX_DEPLOY_MODE env var in the Deploy job to distinguish tag vs. branch deployments based on ref.

Changes

Cohort / File(s) Summary
CI workflow triggers and deploy mode
\.github/workflows/build-test-deploy.yml
- Add on.push.tags: '*' to trigger on tags
- Extend on.push.branches to include master, develop, and project/**
- Compute VORTEX_DEPLOY_MODE as tag when ref starts with refs/tags/, else branch
- Expose VORTEX_DEPLOY_MODE in Deploy job env

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant GH as GitHub
  participant WF as build-test-deploy.yml
  participant Deploy as Deploy Job

  Dev->>GH: Push commit or create tag
  GH->>WF: Trigger workflow (push on branches/tags)
  alt Tag ref (refs/tags/...)
    WF->>Deploy: Start with env VORTEX_DEPLOY_MODE=tag
  else Branch ref
    WF->>Deploy: Start with env VORTEX_DEPLOY_MODE=branch
  end
  Deploy->>Deploy: Execute deployment steps using mode
  Deploy-->>GH: Job status
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

Confirmed

Poem

A tag hops in—thump, thump—what a sign!
Branches wave leaves on the pipeline vine.
I twitch my ears: “Tag or branch today?”
VORTEX whispers, “Mode set—deploy away!”
Carrots compiled, releases aligned—
Happy hops to production, nicely timed. 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly and accurately describes the primary change of ensuring GitHub Actions deployment triggers on tags by fixing the deployment trigger logic, aligning directly with the pull request’s main update.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/fix-artifact-tags-deployment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d76ed61 and c9d1c17.

⛔ Files ignored due to path filters (17)
  • .vortex/installer/tests/Fixtures/install/_baseline/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/db_download_source_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/deploy_type_none_gha/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/hosting_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/provision_profile/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/theme_claro/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/theme_olivero/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/theme_stark/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_groups_no_be_lint/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_groups_no_be_tests/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_no_behat/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_no_phpcs/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_no_phpmd/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_no_phpstan/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_no_phpunit/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_no_rector/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/install/tools_none/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (1)
  • .github/workflows/build-test-deploy.yml (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.github/workflows/**

📄 CodeRabbit inference engine (CLAUDE.md)

Store GitHub Actions workflows under .github/workflows when using GitHub Actions for CI/CD

Files:

  • .github/workflows/build-test-deploy.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (14)
  • GitHub Check: build (0)
  • GitHub Check: build (1)
  • GitHub Check: vortex-test-workflow (3)
  • GitHub Check: vortex-test-workflow (4)
  • GitHub Check: vortex-test-workflow (0)
  • GitHub Check: vortex-test-workflow (2)
  • GitHub Check: vortex-test-workflow (1)
  • GitHub Check: vortex-test-common
  • GitHub Check: vortex-test-deployment (1)
  • GitHub Check: vortex-test-deployment (0)
  • GitHub Check: vortex-test-installer (8.2)
  • GitHub Check: vortex-test-installer (8.4)
  • GitHub Check: vortex-test-installer (8.3)
  • GitHub Check: vortex-test-docs
🔇 Additional comments (2)
.github/workflows/build-test-deploy.yml (2)

12-23: Tag trigger expansion aligns with deployment goal
Including master, develop, and a catch-all tag pattern ensures the workflow fires for release tags while keeping branch coverage intact. Configuration looks correct.


460-472: VORTEX_DEPLOY_MODE derivation is sound
The expression cleanly distinguishes tag vs. branch pushes without affecting existing env vars. Downstream scripts can now branch on the deployment mode.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot temporarily deployed to commit September 29, 2025 09:24 Inactive
@codecov
Copy link

codecov bot commented Sep 29, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.95%. Comparing base (d76ed61) to head (c9d1c17).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #2039   +/-   ##
========================================
  Coverage    63.95%   63.95%           
========================================
  Files           91       91           
  Lines         5637     5637           
  Branches        44       44           
========================================
  Hits          3605     3605           
  Misses        2032     2032           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@AlexSkrypnyk AlexSkrypnyk merged commit 142df8e into develop Sep 29, 2025
31 checks passed
@AlexSkrypnyk AlexSkrypnyk deleted the feature/fix-artifact-tags-deployment branch September 29, 2025 09:56
@github-project-automation github-project-automation bot moved this from BACKLOG to Release queue in Vortex Sep 29, 2025
@AlexSkrypnyk AlexSkrypnyk added this to the 25.10.0 milestone Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Released in 25.10.0

Development

Successfully merging this pull request may close these issues.

[WORKFLOW] Tag deployment does not get triggered in GHA

2 participants