ci(#2495): add fullsend bot actors to e2e trusted bot list - #5429
Conversation
The e2e authorization gate (check-e2e-authorization.sh) only recognized renovate-fullsend[bot] as a trusted bot. PRs authored by fullsend-ai-coder[bot] and fullsend-ai-fix[bot] had author_association=NONE and required manual ok-to-test label application before e2e tests would run, meaning e2e-modifying changes could merge without e2e validation. Add fullsend-ai-coder[bot] and fullsend-ai-fix[bot] to the TRUSTED_BOT_LOGINS list so the is_trusted_bot() check authorizes them for e2e test execution. Add corresponding test cases. Note: pre-commit could not run in the sandbox (git fetch blocked by network policy). The post-script runs pre-commit authoritatively on the runner. Closes #2495
|
🤖 Finished Review · ✅ Success · Started 12:18 AM UTC · Completed 12:27 AM UTC |
Site previewPreview: https://bdf50570-site.fullsend-ai.workers.dev Commit: |
ReviewFindingsMedium
Labels: PR modifies CI e2e authorization scripts |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
/fs-fix
|
|
🤖 Finished Fix · ✅ Success · Started 6:08 AM UTC · Completed 6:13 AM UTC |
fullsend-ai-fix[bot] is not a real GitHub App identity — the fix agent reuses the coder app (slug: fullsend-ai-coder), so its PRs are authored as fullsend-ai-coder[bot]. Remove the phantom identity from TRUSTED_BOT_LOGINS and its corresponding test case. Addresses review feedback on #5429
🔧 Fix agent — iteration 1 (human-triggered)Removed the phantom fullsend-ai-fix[bot] identity from TRUSTED_BOT_LOGINS and its test case per human instruction. The fix agent uses fullsend-ai-coder[bot] (slug: fullsend-ai-coder), so only renovate-fullsend[bot] and fullsend-ai-coder[bot] remain. All 32 tests pass. Fixed (2):
Tests: passed Updated by fullsend fix agent |
E2E tests did not runE2E tests run automatically for org/repo members and collaborators on pull requests. For other contributors, a maintainer must add the See E2E testing guide for details. |
1 similar comment
E2E tests did not runE2E tests run automatically for org/repo members and collaborators on pull requests. For other contributors, a maintainer must add the See E2E testing guide for details. |
|
🤖 Finished Retro · ✅ Success · Started 6:40 AM UTC · Completed 6:52 AM UTC |
Retro: PR #5429 — Add fullsend bot actors to e2e trusted bot listTimeline
Key Finding: Multi-Agent Misinformation CascadeThe phantom Workflow Quality
Related Existing Issues (not proposing duplicates)
Proposals filed
|
Summary
Add
fullsend-ai-coder[bot]andfullsend-ai-fix[bot]to the trusted bot list in the e2e authorization gate script, so bot-authored PRs touching e2e paths automatically get e2e test execution without requiring manualok-to-testlabel application.Related Issue
Closes #2495
Changes
fullsend-ai-coder[bot]andfullsend-ai-fix[bot]toTRUSTED_BOT_LOGINSinscripts/check-e2e-authorization.shscripts/check-e2e-authorization-test.shverifying both new bot actors are authorized via the trusted bot pathTesting
check-e2e-authorization-test.shtests pass, including 2 new tests for the fullsend bot actorsmake lintcould not run (sandbox network restriction); post-script runs pre-commit authoritativelyCloses #2495
Post-script verification
agent/2495-trusted-bot-e2e-auth)6ef9152c619fe81daeb47b3df138b2f72626d456..HEAD)