Aligent GitHub Workflows

A collection of GitHub action workflows. Built using the reusable workflows guide from GitHub.

Documentation

Workflow	Description
AWS CDK	Multi-environment infrastructure synthesis, diffs and deployments with automatic package manager detection
Gadget App Deployment	Gadget app deployment with push, test, and production deployment stages
Magento Cloud Deployment	Magento Cloud deployment with optional NewRelic monitoring and CST reporting
Node Pull Request Checks	Pull request quality checks for Node.js projects
Nx Serverless Deployment	Serverless deployment workflow for Nx monorepos
PHP Quality Checks	Static analysis, coding standards validation, and testing with coverage reporting
S3 Deployment	Deploy assets to S3 buckets

Test Github Workflows Locally using Act

Refer to https://aligent.atlassian.net/wiki/x/JgDjAwE on guidance to test these Workflows locally

CST Reporting Configuration

The CST (Confidentiality and Security Team) reporting feature can be configured in two ways:

1. Workspace-level configuration (recommended):

   • Set CST_ENDPOINT as a repository/organization variable (base URL, e.g., https://package.report.aligent.consulting)
   • Set CST_PROJECT_KEY as a repository/organization variable (your project identifier)
   • Set CST_REPORTING_TOKEN as a repository/organization secret
   • The workflow will automatically use these when available

2. Input overrides (optional):

   • Use cst-endpoint input to override the workspace variable (base URL)
   • Use cst-project-key input to override the workspace variable (project identifier)
   • Use cst-reporting-key input to override the workspace secret
   • Useful for testing or special deployments

The workflow constructs the full CST URL as: {endpoint}/{project-key}/adobe-commerce

CST reporting only runs when endpoint, project key, and auth key are all configured. If any are missing, the step is skipped with an informational message.