docs(#6840): remove stale e2e role from user-facing docs - #6841
Open
fullsend-ai-coder[bot] wants to merge 1 commit into
Open
docs(#6840): remove stale e2e role from user-facing docs#6841fullsend-ai-coder[bot] wants to merge 1 commit into
fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
PR #6771 removed the e2e row from the Role Permissions Matrix in infrastructure-reference.md but two other user-facing docs still listed e2e as a valid role value: - bring-your-own-agent.md: removed e2e from the valid-values list for the roles config field, since e2e is not user-selectable - mint.md: removed e2e from the --roles flag example and added a note that e2e is internal-only The structural fix of consolidating role definitions to prevent future drift is tracked in #2449. Closes #6840
Site previewPreview: https://50aebfaa-site.fullsend-ai.workers.dev Commit: |
|
🤖 Finished Review · ✅ Success · Started 10:01 AM UTC · Completed 10:13 AM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.48 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Risk Assessment: moderate (2/5) DetailsTrivial 2-line docs cleanup by a known bot removing stale e2e references, with no protected paths, security-sensitive files, or dependency changes; elevated slightly to moderate due to high multi-author churn in these documentation files over 90 days. |
|
Looks good to me |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
fullsend-ai-review
Bot
added
the
ready-for-merge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove stale
e2erole references from two user-facing documentation files. PR #6771 removed thee2erow from the Role Permissions Matrix but left references inbring-your-own-agent.mdandmint.md, creating role-selection confusion described in #6563.Related Issue
Closes #6840
Changes
docs/guides/user/bring-your-own-agent.md: Removede2efrom the valid-values list for therolesconfig field. The list now shows only user-selectable roles:fullsend,triage,coder,review,fix,retro,prioritize.docs/cli/mint.md: Removede2efrom the--rolesflag example and added a note that thee2erole is internal-only and not intended for user configuration.Testing
grep -rn 'e2e' docs/guides/user/bring-your-own-agent.md | grep -i 'role'returns zero resultsgrep -rn 'e2e' docs/cli/mint.md | grep -i 'role'returns only the internal-only qualifierChecklist
!for breaking changes)Closes #6840
Post-script verification
agent/6840-remove-stale-e2e-role-refs)1527cab09889257bcc7a40445ff0bccbc0b500a1..HEAD)