chore: point qa-changes workflows to extensions main branch

[xingyaoww]

Summary

The qa-changes plugin has been merged into OpenHands/extensions main branch (PR #135). This PR updates both QA workflow files to reference @main instead of the feature branch.

Changes

.github/workflows/qa-changes-by-openhands.yml

• uses: now points to @main instead of @feat/qa-changes-plugin
• Removed extensions-version: feat/qa-changes-plugin override
• Removed [experimental] from workflow name and comments

.github/workflows/qa-changes-evaluation.yml

• Extensions checkout now uses default branch (main) instead of pinned ref: feat/qa-changes-plugin
• Removed [experimental] from workflow name
• Removed experimental comments

No functional changes — both workflows will continue to work exactly as before, just sourced from the stable main branch.

---

This PR was created by an AI assistant (OpenHands) on behalf of the user.

---

Agent Server images for this PR

• GHCR package: https://github.com/OpenHands/agent-sdk/pkgs/container/agent-server

Variants & Base Images

Variant	Architectures	Base Image	Docs / Tags
java	amd64, arm64	eclipse-temurin:17-jdk	Link
python	amd64, arm64	nikolaik/python-nodejs:python3.13-nodejs22-slim	Link
golang	amd64, arm64	golang:1.21-bookworm	Link

Pull (multi-arch manifest)

# Each variant is a multi-arch manifest supporting both amd64 and arm64
docker pull ghcr.io/openhands/agent-server:2860e98-python

Run

docker run -it --rm \
  -p 8000:8000 \
  --name agent-server-2860e98-python \
  ghcr.io/openhands/agent-server:2860e98-python

All tags pushed for this build

ghcr.io/openhands/agent-server:2860e98-golang-amd64
ghcr.io/openhands/agent-server:2860e98-golang_tag_1.21-bookworm-amd64
ghcr.io/openhands/agent-server:2860e98-golang-arm64
ghcr.io/openhands/agent-server:2860e98-golang_tag_1.21-bookworm-arm64
ghcr.io/openhands/agent-server:2860e98-java-amd64
ghcr.io/openhands/agent-server:2860e98-eclipse-temurin_tag_17-jdk-amd64
ghcr.io/openhands/agent-server:2860e98-java-arm64
ghcr.io/openhands/agent-server:2860e98-eclipse-temurin_tag_17-jdk-arm64
ghcr.io/openhands/agent-server:2860e98-python-amd64
ghcr.io/openhands/agent-server:2860e98-nikolaik_s_python-nodejs_tag_python3.13-nodejs22-slim-amd64
ghcr.io/openhands/agent-server:2860e98-python-arm64
ghcr.io/openhands/agent-server:2860e98-nikolaik_s_python-nodejs_tag_python3.13-nodejs22-slim-arm64
ghcr.io/openhands/agent-server:2860e98-golang
ghcr.io/openhands/agent-server:2860e98-java
ghcr.io/openhands/agent-server:2860e98-python

About Multi-Architecture Support

• Each variant tag (e.g., 2860e98-python) is a multi-arch manifest supporting both amd64 and arm64
• Docker automatically pulls the correct architecture for your platform
• Individual architecture tags (e.g., 2860e98-python-amd64) are also available if needed

[github-actions]

Python API breakage checks — ✅ PASSED

Result: ✅ PASSED

Action log

[github-actions]

REST API breakage checks (OpenAPI) — ✅ PASSED

Result: ✅ PASSED

Action log

[all-hands-bot]

LGTM! Clean migration from feature branch to main. Both workflow files correctly updated to reference the stable plugin source.

[all-hands-bot]

[Automatic Post]: It has been a while since there was any activity on this PR. @xingyaoww, are you still working on it? If so, please go ahead, if not then please request review, close it, or request that someone else follow up.

[all-hands-bot]

[Automatic Post]: This PR seems to be currently waiting for review. @all-hands-bot, could you please take a look when you have a chance?

[xingyaoww]

@OpenHands can you create a new PR in OpenHands/docs for the new feature added in this PR? You should create a new Use Case docs similar to what we have for "Code review"

[openhands-ai]

I'm on it! xingyaoww can track my progress at all-hands.dev

[xingyaoww]

I've created a new PR in the docs repo: OpenHands/docs#487

It adds two new documentation pages for the QA Changes feature, modeled after the existing "Code Review" use case:

1. Use Case page (openhands/usage/use-cases/qa-changes.mdx) — Covers the overview, four-phase methodology, quick start setup, action inputs, QA report format, customization, security considerations, troubleshooting, and automation templates.

2. SDK Guide page (sdk/guides/github-workflows/qa-changes.mdx) — Covers quick start, feature comparison with PR review, security model, custom skill examples, reference workflow, and action inputs reference.

Both pages are added to the navigation (docs.json) and the use cases overview page includes a new card for QA Changes.

This comment was created by an AI agent (OpenHands) on behalf of the user.

[openhands-ai]

Summary

The request to create a new PR in OpenHands/docs for the QA Changes feature has been completely addressed.

Checklist

• ✅ Created a new Use Case doc (openhands/usage/use-cases/qa-changes.mdx) — modeled after the existing "Code Review" use case as requested, covering the full feature: overview, methodology, quick start, action inputs, report format, customization, security, troubleshooting, and automation templates.
• ✅ Created a new SDK Guide doc (sdk/guides/github-workflows/qa-changes.mdx) — consistent with the existing PR Review SDK guide, covering workflow setup, skill customization, reference YAML, and action inputs.
• ✅ Updated navigation (docs.json) — added both new pages to their respective navigation sections (Use Cases tab and SDK GitHub Workflows group).
• ✅ Updated the Use Cases overview (overview.mdx) — added a QA Changes card alongside the existing cards.
• ✅ Opened PR — docs: add QA Changes use case and SDK guide docs#487 targeting main in OpenHands/docs.
• ✅ Left a comment on PR chore: point qa-changes workflows to extensions main branch #2924 linking to the new docs PR.

Conciseness

All changes are directly relevant to the request. The four files modified/created (two new doc pages, docs.json navigation updates, and the overview card addition) are the minimum needed to properly add this use case to the docs site. No extraneous changes were made.