Dev

[Av3boy]

<Issue number> <Change title>

Contents

This PR is trying to resolve:
TBD

We resolve it by:
TBD

Checklist

• I have merged the latest changes from main to my branch.
• I have tested my changes and any affected components.
• I have added the proper documentation about my changes
• I have made sure there is no overlapping work.
• I have discussed any / all issues brought up from code review.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR removes several GitHub Actions workflows and the workflows README under .github/workflows/, leaving publish-core.yml as the only remaining workflow in the repository. As a result, any CI/CD previously handled by the deleted workflows (Web Portal, Asset Store, Docs, and Launcher/test workflows) will no longer run unless there is an external replacement process.

Changes:

• Deleted Azure Static Web Apps deployment workflows for the Web Portal and Asset Store.
• Deleted placeholder/test workflows for Docs and Launcher.
• Removed .github/workflows/README.md that documented the pipeline setup.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.github/workflows/README.md	Removed pipeline documentation (no replacement added).
.github/workflows/publish-web.yml	Removed Web Portal deployment workflow.
.github/workflows/publish-launcher.yml	Removed Launcher/test workflow.
.github/workflows/publish-docs.yml	Removed Docs publishing workflow.
.github/workflows/publish-asset-store.yml	Removed Asset Store deployment workflow.
.github/workflows/azure-static-web-apps-victorious-moss-06d128203.yml	Removed auto-generated Azure Static Web Apps CI/CD workflow.

Comments suppressed due to low confidence (6)

.github/workflows/publish-web.yml:1

• This workflow is being removed entirely, which would disable the GitHub Actions-based deployment for the Web Portal. If deployments are still required, keep a replacement workflow (or document the new deployment mechanism) and update the PR description to explicitly state that Web Portal CI/CD is being decommissioned.
  .github/workflows/publish-asset-store.yml:1
• Removing this workflow disables Asset Store CI/CD (including Static Web Apps deployment and PR close cleanup). If Asset Store is still an active component, add a replacement deployment pipeline or move this workflow to a clearly disabled state (e.g., manual dispatch) with documentation explaining why it’s not triggered automatically anymore.
  .github/workflows/azure-static-web-apps-victorious-moss-06d128203.yml:1
• This auto-generated Azure Static Web Apps CI/CD workflow is being deleted and there is no other workflow in the repo that deploys the web UI (no remaining uses of Azure/static-web-apps-deploy). If the Static Web App is still meant to be updated from main/PRs, keep an equivalent workflow or document the replacement deployment process in the repo.
  .github/workflows/README.md:1
• The workflows documentation (.github/workflows/README.md) is being removed and there doesn’t appear to be any replacement documentation elsewhere in the repo. If these pipelines are still relevant (even if temporarily disabled), move this documentation to a more appropriate location (e.g., /docs or root README) or add an updated replacement so contributors can understand how releases/deployments are supposed to work.
  .github/workflows/publish-launcher.yml:1
• The PR description is still “TBD” for both the problem statement and the solution. Given this PR removes multiple CI/CD workflows, please update the PR description to explain the intent (decommission vs. migrate) and what should replace these pipelines operationally.
  .github/workflows/publish-docs.yml:1
• Deleting this workflow removes any GitHub Actions path to publish documentation. If docs deployment is still required, add a replacement workflow (or document the new publishing process) so docs updates aren’t silently stopped.

---

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