Skip to content

chore: migrate wrapper to call Master Workflow.yml directly - #5

Open
SkylineCICD wants to merge 1 commit into
mainfrom
chore/wrapper-migration-internal-nuget
Open

chore: migrate wrapper to call Master Workflow.yml directly#5
SkylineCICD wants to merge 1 commit into
mainfrom
chore/wrapper-migration-internal-nuget

Conversation

@SkylineCICD

Copy link
Copy Markdown

This PR was opened automatically by the
Wrapper Migration Workflow in
SkylineCommunications/_ReusableWorkflows.

What changed

The wrapper workflow file(s) in .github/workflows/ were
updated to call
SkylineCommunications/_ReusableWorkflows/.github/workflows/Master Workflow.yml
directly instead of the legacy
internal-nuget master wrapper. Input and
secret names were renamed to the kebab-case / SHOUTING_CASE
names that Master Workflow.yml expects, and any obsolete
passthrough inputs (referenceName, runNumber,
referenceType, repository, owner, …) were dropped.

Why

The legacy NuGet Solution, Internal NuGet Solution and
DataMiner App Packages master workflows are thin wrappers
that internally call Master Workflow.yml. Removing the
indirection:

  • shortens the CI call chain by one job;
  • exposes the full set of Master Workflow.yml inputs
    (e.g. runs-on) without us having to forward each one
    through every wrapper;
  • lets us evolve the master inputs without breaking
    callers.

Review checklist

  • The rewrite preserves all with: values that were
    previously passed through (only the keys were
    renamed).
  • All secrets: mappings are intact.
  • If your wrapper job had extra steps or conditions
    around the legacy uses: call, verify they still
    make sense pointing at the master workflow.
  • CI on this PR is green.

Idempotent: re-running the legacy wrapper while this PR
is open will not create another one.

The 'internal-nuget' legacy master workflow is a
thin wrapper around Master Workflow.yml. Removing it shortens
the call chain by one job, exposes the full set of
Master Workflow inputs (e.g. runs-on), and lets us evolve
inputs without breaking callers.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@SkylineCICD SkylineCICD added the wrapper-migration Migrate caller from legacy redirecting master workflow to Master Workflow.yml label May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wrapper-migration Migrate caller from legacy redirecting master workflow to Master Workflow.yml

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant