Skip to content

fix: support comma-separated application names in translate setup workflow - #289

Draft
pbitla-sonata with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-failing-github-actions-job
Draft

fix: support comma-separated application names in translate setup workflow#289
pbitla-sonata with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-failing-github-actions-job

Conversation

Copilot AI commented Aug 5, 2026

Copy link
Copy Markdown

The _translate-setup.yml reusable workflow only accepted a single application_name, causing the job to fail when a user passed multiple app names as a comma-separated string (e.g. frontend-app-learner-portal-enterprise, frontend-app-admin-portal).

Changes

  • _translate-setup.yml: Parse application_name as a comma-separated list; validate each entry individually; filter the matrix to all matching apps
  • Caller workflows (translate-json-source-strings.yml, seed-json-translations.yml, translate-po-source-strings.yml, seed-po-translations.yml): Updated application_name input descriptions to document comma-separated support

Before: entire comma-separated string treated as a single (invalid) app name → core.setFailed

After:

const selectedApps = appInput
  ? appInput.split(',').map(s => s.trim()).filter(Boolean)
  : [];
// validates and filters each app independently

…kflow

Co-authored-by: pbitla-sonata <235820339+pbitla-sonata@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix the failing GitHub Actions job setup fix: support comma-separated application names in translate setup workflow Aug 5, 2026
Copilot AI requested a review from pbitla-sonata August 5, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants