Notify when there is CI is failing

[hjetpoluru]

What is this about?

If there is a CI failure due to a code change, we should dynamically report the failure in the extension chat for increased visibility and quicker actions.

Scenario

No response

Design

No response

Technical Details

Potential approach suggested by Desi https://circleci.com/docs/slack-orb-tutorial/

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• [ ] Engineering (needed in most cases)
• [ ] Design
• [ ] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

https://consensys.slack.com/archives/CTQAGKY5V/p1725541071251659

[gauthierpetetin]

Comment from technical refinement:

• Requires access to CircleCI webhooks. which any repository admin would have access
• Shall we wait until merge queues are on, before working on this? Value might be lower if merge queues already allow to prevent most CI failures