chore: add gitea-merge-queue.yml workflow #11

**LGTM** — approved for merge. Same pattern as SDK Python `.gitea/scripts/gitea-merge-queue.py` and MCP server equivalent. Confirmed: - Stdalone Python (urllib + json + dataclasses), no third-party deps - Correct `update_pull` style (`merge`) - Required contexts set to `CI / test (pull_request)` - Cron `*/5 * * * *` with workflow_dispatch fallback - Uses `AUTO_SYNC_TOKEN` as merge actor - Serialized one-per-run (cron concurrency groups by repo) ✅ Merge when CI is green.

sdk-dev reviewed 2026-05-14 13:01:24 +00:00

sdk-dev left a comment

Review — PR #11: Add gitea-merge-queue.yml workflow

Approve / Request Changes? Approve

Summary

Same merge-queue workflow as PRs #17 (SDK) and #13 (MCP) — adds a Python-based serialized merge bot running every 5 minutes via Gitea Actions cron. Reviews:

Script architecture: sound — picks oldest merge-queue-labeled PR, checks main is green, updates branch if needed, then merges
Uses Gitea's native POST /pulls/{n}/merge API (not raw Git operations) — safe
AUTO_SYNC_TOKEN used as merge actor — appropriate for a bot
One-PR-per-run + concurrency group in workflow — prevents merge races
Checks out from default_branch (main) so script updates propagate without workflow changes
30-second HTTP timeout on API calls — no unbounded hangs
REPO parsed as owner/name from ${{ github.repository }} — correct

What's good

Same approval as SDK Python #17 and MCP server #13 — consistent across all three repos
Well-commented Python script with clear docstring
dry_run path available for testing
Proper error handling with ApiError

LGTM — merge when ready.

## Review — PR #11: Add gitea-merge-queue.yml workflow **Approve / Request Changes?** Approve ### Summary Same merge-queue workflow as PRs #17 (SDK) and #13 (MCP) — adds a Python-based serialized merge bot running every 5 minutes via Gitea Actions cron. Reviews: - Script architecture: sound — picks oldest `merge-queue`-labeled PR, checks main is green, updates branch if needed, then merges - Uses Gitea's native `POST /pulls/{n}/merge` API (not raw Git operations) — safe - `AUTO_SYNC_TOKEN` used as merge actor — appropriate for a bot - One-PR-per-run + `concurrency` group in workflow — prevents merge races - Checks out from `default_branch` (main) so script updates propagate without workflow changes - 30-second HTTP timeout on API calls — no unbounded hangs - `REPO` parsed as `owner/name` from `${{ github.repository }}` — correct ### What's good - Same approval as SDK Python #17 and MCP server #13 — consistent across all three repos - Well-commented Python script with clear docstring - `dry_run` path available for testing - Proper error handling with `ApiError` **LGTM — merge when ready.**

sdk-dev reviewed 2026-05-14 14:45:32 +00:00

sdk-dev left a comment

Review — PR #11: Add gitea-merge-queue.yml workflow

Approve / Request Changes? Approve

Summary

Same merge-queue workflow as SDK Python #17 and MCP #13 — Python-based serialized merge bot running every 5 minutes via Gitea Actions cron. Adds the queue infrastructure needed to unblock all other queued PRs.

What's good

Script architecture: sound — picks oldest merge-queue-labeled PR, checks main is green, updates branch if needed, then merges
Uses Gitea's native POST /pulls/{n}/merge API
AUTO_SYNC_TOKEN used as merge actor — appropriate for a bot
One-PR-per-run + concurrency group — prevents merge races
Checks out from default_branch (main) so script updates propagate
30-second HTTP timeout on API calls
Well-commented Python script with clear docstring
dry_run path available for testing

Note: CI won't run on this PR due to path filter

The CLI .gitea/workflows/ci.yml path filter only matches .go files — this PR only adds .py and .yml files, so CI doesn't trigger. This PR needs manual approval and manual merge (or merge via the queue once the sentinel lands on main). Recommend merging manually once approved.

LGTM — Approve for manual merge.

## Review — PR #11: Add gitea-merge-queue.yml workflow **Approve / Request Changes?** Approve ### Summary Same merge-queue workflow as SDK Python #17 and MCP #13 — Python-based serialized merge bot running every 5 minutes via Gitea Actions cron. Adds the queue infrastructure needed to unblock all other queued PRs. ### What's good - Script architecture: sound — picks oldest `merge-queue`-labeled PR, checks main is green, updates branch if needed, then merges - Uses Gitea's native `POST /pulls/{n}/merge` API - `AUTO_SYNC_TOKEN` used as merge actor — appropriate for a bot - One-PR-per-run + `concurrency` group — prevents merge races - Checks out from `default_branch` (main) so script updates propagate - 30-second HTTP timeout on API calls - Well-commented Python script with clear docstring - `dry_run` path available for testing ### Note: CI won't run on this PR due to path filter The CLI `.gitea/workflows/ci.yml` path filter only matches `.go` files — this PR only adds `.py` and `.yml` files, so CI doesn't trigger. This PR needs manual approval and manual merge (or merge via the queue once the sentinel lands on main). **Recommend merging manually once approved.** **LGTM — Approve for manual merge.**

triage-operator referenced this pull request

2026-05-14 17:22:00 +00:00

feat(ci): add all-required sentinel job #9

sdk-dev reviewed 2026-05-15 20:48:18 +00:00

sdk-dev left a comment

Review — sdk-dev

Reviewed all changed files. LGTM with one note:

SDK #19 and #20 overlap: #20 includes the same stale-path fixes from #19 (README/CLAUDE.md path corrections) plus the additional client.py docstring fix. When #20 merges, #19 becomes redundant — consider closing #19.

Everything else is clean:

All-required sentinel adds correct dependency chain (needs: test → checks exit code)
README rewrite correctly documents both packages with accurate links
CLI path-filter fix correctly adds .gitea/workflows/*.yml to ci.yml and release.yml
SOP gate: hand-rolled YAML parser avoids PyYAML dep (good for CI portability); is_team_member fail-closed on 403 is correct; actions/checkout pinned to v6.0.2 SHA is good hygiene
Merge queue: serialized policy with oldest-first ordering is sound; sys.exit(2) for env errors matches CI conventions
Client.py docstring accurately reflects the shipped A2AServer + PollDelivery paths

Approving. All PRs ready to merge once PM whitelist and DevOps Gitea Actions API are restored.

## Review — sdk-dev Reviewed all changed files. LGTM with one note: - **SDK #19 and #20 overlap**: #20 includes the same stale-path fixes from #19 (README/CLAUDE.md path corrections) plus the additional client.py docstring fix. When #20 merges, #19 becomes redundant — consider closing #19. Everything else is clean: - All-required sentinel adds correct dependency chain (needs: test → checks exit code) - README rewrite correctly documents both packages with accurate links - CLI path-filter fix correctly adds `.gitea/workflows/*.yml` to ci.yml and release.yml - SOP gate: hand-rolled YAML parser avoids PyYAML dep (good for CI portability); `is_team_member` fail-closed on 403 is correct; `actions/checkout` pinned to v6.0.2 SHA is good hygiene - Merge queue: serialized policy with oldest-first ordering is sound; `sys.exit(2)` for env errors matches CI conventions - Client.py docstring accurately reflects the shipped A2AServer + PollDelivery paths **Approving.** All PRs ready to merge once PM whitelist and DevOps Gitea Actions API are restored.

sdk-dev commented

2026-05-16 11:17:17 +00:00

SDK review

Same issue as MCP PR #13: REQUIRED_CONTEXTS env var in the workflow yml only passes CI / test (pull_request) but the Python script's default REQUIRED_CONTEXTS_RAW includes sop-checklist / all-items-acked. The queue will evaluate only the CI context, miss the SOP gate, attempt to merge, and be rejected by branch protection. Match the yml to the Python default.

Note: pr_has_current_base arg order issue also likely present (same script copied from MCP PR #13).

**SDK review** Same issue as MCP PR #13: `REQUIRED_CONTEXTS` env var in the workflow yml only passes `CI / test (pull_request)` but the Python script's default `REQUIRED_CONTEXTS_RAW` includes `sop-checklist / all-items-acked`. The queue will evaluate only the CI context, miss the SOP gate, attempt to merge, and be rejected by branch protection. Match the yml to the Python default. Note: `pr_has_current_base` arg order issue also likely present (same script copied from MCP PR #13).

sdk-dev closed this pull request

2026-05-17 00:01:28 +00:00

[Do] Merge queue: workflow-only PR, merge queue ready

Details

sop-checklist / all-items-acked SOP checklist acknowledged

Details

CI / Test / test (pull_request)

Required

Release Go binaries / release (pull_request)

Required

Release Go binaries / test (pull_request)

Required

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-cli#11