Downstream Repository Health Report
This report covers bot activity in downstream repositories using elastic/ai-github-actions workflows for the past 24 hours.
Monitored Repositories
elastic/ai-github-actions-playground
elastic/beats
elastic/elastic-agent
elastic/infra-party
elastic/integrations
elastic/oblt-aw
Issues Found
1. elastic/elastic-agent — repeated Copilot auth failures in scheduled workflow comments
Location:
Workflow: Code Quality Audit; Docs Patrol; Breaking Change DetectorProblem: Bot comments repeatedly report engine termination before producing output due to missing authentication.User Impact: Workflows fail to produce task outputs and instead post failure comments.Evidence:
"⚠️ Engine Failurecopilot engine terminated before producing output."
"Authentication failed ..."
"No authentication information found."
2. elastic/ai-github-actions-playground — recurring Copilot auth failures and Gemini invalid API key failures
Location:
Copilot auth failures:
Gemini API key failures:
Workflow: Project Summary; Bug Hunter; Stale Issues Investigator; Framework Best Practices; UX Design Patrol; Breaking Change Detector; Code Duplication Detector; Scheduled Audit; Internal Gemini CLI; Internal Gemini CLI Web SearchProblem: Repeated engine failures from missing Copilot auth and invalid Gemini API key.User Impact: Multiple workflows are non-functional and emit repeated failure noise instead of useful outputs.Evidence:
"⚠️ Engine Failurecopilot engine terminated before producing output."
"Authentication failed ..."
"No authentication information found."
"API key not valid. Please pass a valid API key."
status: 400, reason: API_KEY_INVALID
Summary
Total repositories monitored: 6
Total bot interactions reviewed: 19
Issues found: 2
Error categories: authentication failures, invalid API key configuration
Suggested Actions
🔒 Integrity filter blocked 14 items
The following items were blocked because they don't meet the GitHub integrity level.
#18660 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#18648 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#707 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#18279 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#17876 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#50329 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#50328 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#50286 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#50297 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#50223 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#49160 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#49159 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#17542 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".#16025 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools :
github :
min-integrity : approved # merged | approved | unapproved | none
What is this? | From workflow: Trigger Internal Downstream Health
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Downstream Repository Health Report
This report covers bot activity in downstream repositories using
elastic/ai-github-actionsworkflows for the past 24 hours.Monitored Repositories
Issues Found
1.
elastic/elastic-agent— repeated Copilot auth failures in scheduled workflow commentsLocation:
Workflow: Code Quality Audit; Docs Patrol; Breaking Change Detector
Problem: Bot comments repeatedly report engine termination before producing output due to missing authentication.
User Impact: Workflows fail to produce task outputs and instead post failure comments.
Evidence:
copilotengine terminated before producing output."2.
elastic/ai-github-actions-playground— recurring Copilot auth failures and Gemini invalid API key failuresLocation:
Workflow: Project Summary; Bug Hunter; Stale Issues Investigator; Framework Best Practices; UX Design Patrol; Breaking Change Detector; Code Duplication Detector; Scheduled Audit; Internal Gemini CLI; Internal Gemini CLI Web Search
Problem: Repeated engine failures from missing Copilot auth and invalid Gemini API key.
User Impact: Multiple workflows are non-functional and emit repeated failure noise instead of useful outputs.
Evidence:
copilotengine terminated before producing output."status: 400,reason: API_KEY_INVALIDSummary
Suggested Actions
elastic/elastic-agentandelastic/ai-github-actions-playground.elastic/ai-github-actions-playground.Note
🔒 Integrity filter blocked 14 items
The following items were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Trigger Internal Downstream Health
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.