Copilot/fix GitHub actions workflow again

[aaronpowell]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull request overview

This PR fixes the GitHub Actions workflow triggering mechanism by ensuring the website deployment workflow is properly triggered after the publish workflow completes. The previous push-based trigger wouldn't work because pushes made by GITHUB_TOKEN don't trigger other workflows. The solution implements manual workflow dispatch using the GitHub CLI.

Changes:

• Added actions: write permission to the publish workflow to enable workflow dispatch
• Added a manual dispatch step in publish.yml to trigger deploy-website.yml after pushing to main
• Removed the push trigger from deploy-website.yml and made it workflow_dispatch only

Reviewed changes

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

File	Description
.github/workflows/publish.yml	Added actions: write permission and a step to manually dispatch the deploy-website workflow after publishing to main
.github/workflows/deploy-website.yml	Removed push trigger and kept only workflow_dispatch, since GITHUB_TOKEN pushes don't trigger other workflows