[Chidozie Ononiwu (chidozieononiwu)]

This pull request refactors the event-processor.yml GitHub Actions workflow to split event handling into two separate jobs, optimizing resource usage and permissions. Now, only newly opened issues trigger the Azure login and Key Vault secret retrieval, while all other events are handled in a streamlined job without unnecessary Azure steps.

Workflow optimization and job separation:

• Added a new event-handler job to handle all events except newly opened issues, reducing unnecessary Azure login overhead and limiting permissions to only what's needed.
• Updated the event-handler-with-azure job so that Azure login and Key Vault access only occur for newly opened issues, improving efficiency and security.

Permissions and configuration cleanup:

• Removed unnecessary permissions (such as pull-requests: write and contents: read) from the Azure-related job, further tightening security.
• Cleaned up commented-out sections related to building from source, focusing the workflow on installing the released tool version. [1] [2]

https://github.com/microsoft/mcp-pr/issues/733

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
71 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟢 Approval recommended

The complementary job conditions preserve event coverage, with appropriate permissions and no identified blocking issues.

No open issues 🎉

What changed in this PR

Splits event processing into separate jobs so only newly opened issues incur Azure authentication and Key Vault access.

Changes:

• Adds a non-Azure job for all other events.
• Narrows job permissions to their respective needs.
• Removes commented-out build-from-source instructions.

File	Description
.github/​workflows/​event-processor.yml	Separates Azure-dependent processing from other events and reduces permissions.

_{Review effort: Balanced}