Priority

(Low) Something is a little off

Description

When using the command spfx project github workflow add, the package name is used as the path for the sppkg file. While this works for freshly scaffolded SPFx projects (where the sppkg file name matches the project name), it does not account for cases where the sppkg file name has been changed independently from the project name. As a result, if you rename the sppkg file but retain the original project name, the workflow incorrectly fails to locate or reference the sppkg package.

Steps to reproduce

1. Scaffold a new SPFx project.
2. Change the name of the sppkg file without changing the project name.
3. Run spfx project github workflow add.
4. Observe that the workflow uses the original package/project name as the sppkg file path and fails if the actual sppkg file has a different name.

Expected results

The workflow should allow specifying or detecting the actual sppkg file name, rather than assuming it matches the project/package name. This ensures that workflows work for projects where the sppkg file name is customized.

Actual results

The workflow always uses the package/project name as the sppkg file path, which fails when the sppkg file name is changed.

Diagnostics

No response

CLI for Microsoft 365 version

v11.7.0

nodejs version

v24.12.0

Operating system (environment)

Windows

Shell

PowerShell

cli doctor

No response

Additional Info

No response