The NuGet packages are supposed to be built when code is pushed to the "released code" branch (i.e. Any of the released vx.y branches.) This fails to happen for the 2.x branch because the publish_nuget_packages job in the workflow hard-codes the targeted branch to v1.x (i.e. github.ref == 'refs/heads/v1.x' instead of something more general.)
ESTIMATE TBD
Steps to reproduce the issue
Please do NOT test this against the NCIOCPL copy of the NCI.OCPL.Api.Shared repository.
Create a release
Push to the 2.x branch
What's the expected result?
The GitHub actions should create packages with the new release number.
Issue description
The NuGet packages are supposed to be built when code is pushed to the "released code" branch (i.e. Any of the released vx.y branches.) This fails to happen for the 2.x branch because the
publish_nuget_packages
job in the workflow hard-codes the targeted branch tov1.x
(i.e.github.ref == 'refs/heads/v1.x'
instead of something more general.)Steps to reproduce the issue
Please do NOT test this against the NCIOCPL copy of the NCI.OCPL.Api.Shared repository.
What's the expected result?
What's the actual result?
publish_nuget_packages
job is skipped.Additional details / screenshot
Related Tickets