apache/lucene

action failures sent to builds@lucene.apache.org

Open

#14,687 opened on 2025年5月19日

GitHub で見る
 (4 comments) (1 reaction) (0 assignees)Java (2,179 stars) (879 forks)batch import
good first issuetype:enhancement

説明

Description

Some actions that run against main, e.g. on every push, nightly release smoketest and other maintenance tasks. It would be nice if failures were sent to builds@ mailing list.

Currently the notifications are only sent to individuals? My concern is that only those individuals are seeing the issues and debugging them. If we sent the failures to the builds@ list, we could share the love.

https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/notifications-for-workflow-runs

I'm not sure if something like actions/send-email is needed for this, but it is one idea.

コントリビューターガイド

技術スタック
github actionsshell
領域
devopsci cd
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
GitHub Actions knowledgeEmail configuration
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
Review the existing GitHub Actions workflows in the repository (e.g., .github/workflows/). Identify which workflows run on pushes to main and are candidates for failure notifications. Use the GitHub Actions documentation to configure email notifications, possibly via a third party action like actions/send email. Discuss with maintainers whether notifications should go to builds@lucene.apache.org and whether any sensitive information needs to be excluded.