Skip Deliver and Deploy when no app artifacts exist

[Copilot]

❔What, Why & How

This pull request improves the CI/CD workflow for both AppSource App and Per Tenant Extension templates by ensuring that the Deploy and Deliver actions are only executed when app artifacts are present. This prevents errors that could occur on initial commits or when no artifacts are generated.

Workflow improvements for artifact handling:

• Added a conditional check (if: hashFiles('.artifacts/**/*.app') != '') to the Deploy step in Templates/AppSource App/.github/workflows/CICD.yaml and Templates/Per Tenant Extension/.github/workflows/CICD.yaml to skip deployment when no .app artifacts are found.

• Added the same conditional check to the Deliver step in both workflow files to skip delivery when no artifacts are present.

• Added notice steps that display informative messages when Deploy or Deliver steps are skipped due to no app artifacts:

  • "Deployment to environment [name] was skipped because no app artifacts were found"
  • "Delivery to [target] was skipped because no app artifacts were found"

  E.g.

Documentation updates:

• Updated RELEASENOTES.md to document that Deliver and Deploy actions now skip execution when no app artifacts are found, preventing errors on initial commits.
• Updated Scenarios/DeliveryTargets.md to clarify that custom delivery scripts will not execute when delivery is skipped due to missing app artifacts, specifically noting this prevents errors on initial commits when no apps have been built yet.

✅ Checklist

• Add tests (E2E, unit tests)
• Update RELEASENOTES.md
• Update documentation (e.g. for new settings or scenarios)
• Add telemetry

---

Related to #2126

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mazhelez]

@copilot it seems the solution works. However, can you somehow add a notice to the build run that the publish to environment was skipped because there were no generated artifacts?

[Copilot]

@copilot it seems the solution works. However, can you somehow add a notice to the build run that the publish to environment was skipped because there were no generated artifacts?

Added notice steps in commit 5542516. When deployment or delivery is skipped due to no app artifacts, a notice will now appear in the workflow run:

• "Deployment to environment [name] was skipped because no app artifacts were found"
• "Delivery to [target] was skipped because no app artifacts were found"

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mazhelez]

A new version of AL-Go (v9.0) has been released.

Please move your release notes changes to above the ## v9.0 section in the RELEASENOTES.md file.

This ensures your changes are included in the next release rather than being listed under an already-released version.

[Copilot]

Moved to above the v9.0 section in commit 6f63340.

[mazhelez]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts resolved in commit 6f63340. The release notes entry for Issue 2126 is now in the top Issues section (before v9.0), and all changes from main have been merged successfully.

[spetersenms]

A new version of AL-Go (v9.1) has been released.

Please move your release notes changes to above the ## v9.1 section in the RELEASENOTES.md file.

This ensures your changes are included in the next release rather than being listed under an already-released version.

[spetersenms]

A new version of AL-Go (v9.1) has been released.

Please move your release notes changes to above the ## v9.1 section in the RELEASENOTES.md file.

This ensures your changes are included in the next release rather than being listed under an already-released version.

[mazhelez]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

I've resolved the merge conflicts by rebasing the changes onto the latest main branch (which includes v9.1). The changes are now clean and ready:

• Added conditional checks (if: hashFiles('.artifacts/**/*.app') != '') to skip Deploy and Deliver steps when no app artifacts exist
• Added notice steps that display informative messages when steps are skipped
• Moved release notes entry to above the v9.1 section
• Updated documentation in Scenarios/DeliveryTargets.md and Workshop files

The branch is ready but requires a force push to update the PR. The local branch has been reset to main with a clean commit containing all the changes. To complete the update, you'll need to manually force push or I can work with the existing commit history if you have another approach you'd prefer.