Add Verification Stack use case group with QA Changes page#501
Draft
xingyaoww wants to merge 3 commits into
Draft
Add Verification Stack use case group with QA Changes page#501xingyaoww wants to merge 3 commits into
xingyaoww wants to merge 3 commits into
Conversation
- Create verification-stack.mdx: overview of the layered verification system covering Layer 1 (trajectory-level critic), Layer 2 (ReviewBot + QA agent), setup instructions for both GitHub Actions and OpenHands Automations, effectiveness summary, and the iterate skill - Create qa-changes.mdx: QA agent use case page with methodology, quick start, report format, customization, and troubleshooting - Move code-review.mdx under a new 'Verification Stack' nav group alongside qa-changes and the overview page - Update overview.mdx with Verification Stack and QA Testing cards - Update docs.json navigation to nest the three pages under a 'Verification Stack' sub-group within Use Cases Co-authored-by: openhands <openhands@all-hands.dev>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…tions Add a 'Setup Checklist for GitHub Event Automations' section that covers: - GitHub App installation requirements - Team org vs personal org event routing (common pitfall) - Service account setup for bot-driven automations - Complete PR review bot walkthrough example - Troubleshooting tips for when automations don't trigger This addresses a non-obvious gotcha where automations created under a personal org silently never receive events for org repos, because GitHub events are routed to the team org that claimed the GitHub organization. Co-authored-by: openhands <openhands@all-hands.dev>
…nt automations Rewrites the 'Setup Checklist' section (from previous commit) into a more complete 'Prerequisites for GitHub Event Automations' section based on real-world debugging of a silent event delivery failure. Key changes: - Adds 'Claim Your GitHub Organization' as the #1 prerequisite with a Warning callout — this was the actual root cause (missing OrgGitClaim meant events had nowhere to route) - Adds 'Create an OpenHands Team Organization' as a prerequisite step - Links to the existing claiming docs at /openhands/usage/cloud/organizations/settings#claiming-git-organizations - Replaces the flat Tip block with an AccordionGroup troubleshooting section covering the 4 most common failure modes - Updates the summary table to link to prerequisites instead of saying 'None — just create the automation' Co-authored-by: openhands <openhands@all-hands.dev>
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
2 participants
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
Creates a Verification Stack use case group in the docs, grouping the code review and QA agents under a unified section that explains the full verification pipeline. This supports the upcoming blog post by providing a permanent home for detailed setup instructions.
Changes
New pages
verification-stack.mdx— Overview of the layered verification system:qa-changes.mdx— QA agent use case page:Navigation restructuring
code-review.mdxinto a new "Verification Stack" sub-group alongsideverification-stack.mdxandqa-changes.mdxNavigation structure (under Use Cases)
Context
This PR is part of the work for AGE-512. The goal is to provide a permanent docs home for verification stack content so the companion blog post can stay high-level and link here for detailed instructions.
This PR was created by an AI agent (OpenHands) on behalf of the user.
@xingyaoww can click here to continue refining the PR