High Impact Alert Workflow

[overmyheadandbody]

This defines a new workflow that sends notifications to a Slack channel as soon as a PR with a high-impact label is opened. The previous logic from the merge-to-stage.js script has been removed, since we want such a notification to be sent out as soon as the PR is opened, not when it eventually reaches the stage branch, to ensure it gets visibility early on. Additionally, some workflows have been adapted to only run if the owner is adobecom to reduce workflow runs on forks.

Resolves: MWPW-148268

Test URLs:

• Before: https://main--milo--adobecom.hlx.page/?martech=off
• After: https://high-impact-workflow--milo--overmyheadandbody.hlx.page/?martech=off

[aem-code-sync]

Page	Scores	Audits	Google
/?martech=off

[mokimo]

Cool! The only use-case I'm thinking off is adding/removing labels, which would send multiple messages.

We can't easily verify a message has/hasn't already been sent though, since actions are stateless and we can't access slack.

So we need a bit of contributor education to avoid multiple messages because of adding and removing the label

[overmyheadandbody]

I think most non-stage PRs get just one batch of labels, so we'll have to test this in the wild and see if it pollutes the Slack channel. The workflow could add its own label, say notification-triggered, and a PR with such a label would no longer send a notification. Except if someone manually removes it 🙂

[github-actions]

Reminder to set the Ready for Stage label - to queue this to get merged to stage & production.

[mokimo]

I think workflow's cant be merged automatically 😕 That's just a guess though. Some PRs get this error:

Error merging 2346: High Impact Alert Workflow Resource not accessible by integration

We'll need to watch this. It sounds like a security feature so that workflows can't elevate their permissions and take over a repo