✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Summary

This PR adds projectName to secret approval request notifications sent via Slack and Microsoft Teams, making it easier to identify which project triggered the notification when multiple projects share the same channel.

• types.ts — Adds projectName: string to the TNotification payload type for SECRET_APPROVAL events.
• slack-fns.ts — Prepends *Project*: <name> to the Slack message body above Environment.
• microsoft-teams-fns.ts — Inserts a "Project" fact row before "Environment" in the Teams adaptive card.
• secret-approval-request-service.ts — In generateSecretApprovalRequest, adds a new projectDAL.findById(projectId) call to populate the project name. In generateSecretApprovalRequestV2Bridge, reuses the project variable already in scope (no extra DB call needed there). The new lookup in generateSecretApprovalRequest has no null-safety guard — if the lookup ever returns null, accessing project.name would throw a TypeError and propagate up to the caller unexpectedly.

Confidence Score: 4/5

• PR is safe to merge; the core logic is correct and the only concern is a minor missing null guard on a new DB lookup.
• The changes are straightforward additions to an existing notification flow. The V2Bridge path was already cleanly handled. The single new findById call in generateSecretApprovalRequest works in practice (earlier guards ensure the project exists), but a defensive null check would make it more robust.
• backend/src/ee/services/secret-approval-request/secret-approval-request-service.ts — new findById call at line 1626 lacks a null check.

Important Files Changed

_{Last reviewed commit: 7540d80}