labring / labring/laf

[Feature] Send LAF E2E failure message to IM software

Open
#1,121 0 comments 0 reactions 0 assignees View on GitHub
feature
Dominant language
TypeScript
Stars
7.6k
Forks
670
PR merge metrics
No merged PRs in 30d

Description

### Search before asking

- [X] I had searched in the [issues](https://github.com/labring/laf/issues?q=is%3Aissue) and found no similar issues.

### Feature Request

We now have e2e CI, but it's triggered after merging into the main branch, not by a PR. This means we have to frequently check GitHub Actions to see if e2e has failed.

We can add a new action to the e2e actions that automatically sends a message to an IM software, such as lark, if e2e fails.

e2e GitHub Actions YAML: https://github.com/labring/laf/blob/main/.github/workflows/e2e.yml

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with .github/workflows/e2e.yml and review how the existing end-to-end workflow reports failures. Define the supported IM software and required credentials, then verify that a failed e2e run sends a message without affecting the workflow's failure status.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.