Create `ready-for-review` label to unblock auto-review dispatch for code agent PRs

Open Beginner friendly
#3,116 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, shell
Domain
ci-cd

Research direction

Start with workflow run 30613736197, the repository's existing label set, and the post-code.sh behavior described in the issue. Create the ready-for-review label using the proposed gh command, then verify on the next code agent PR that the warning is absent and the review agent is auto-dispatched without /fs-review.

Written by the indexing model from the issue text.

Description

ready-for-triage stale triaged

What happened

On PR #3045, the code agent completed its fix for issue #3041 on Jul 31 and created the PR. The post-code script attempted to apply the ready-for-review label to trigger auto-review dispatch, but the label does not exist in this repository — the post-script logged ##[warning]Failed to apply ready-for-review label to PR #3045 in workflow run 30613736197. Without this label, the review agent was never auto-dispatched. The PR sat idle for 4 days until a human manually ran /fs-review on Aug 4. During those 4 days, the nightly E2E tests continued failing with the same error (confirmed by triage recurrence updates on Aug 1 and Aug 3).

What could go better

The ready-for-review label is a prerequisite for the fullsend auto-review dispatch path on bot-authored PRs. This repository has ready-to-code, ready-for-merge, and ready-for-triage labels but is missing ready-for-review. This is likely an enrollment oversight — the label was never provisioned when fullsend was set up on this repo. The upstream systemic fix (post-code.sh creating labels on-the-fly) is tracked at fullsend-ai/agents#199, #274, #479, #509, and fullsend-ai/fullsend#5187, but none have landed yet. Until those systemic fixes ship, every code agent PR in this repo will require manual /fs-review triggering, adding unnecessary latency. Confidence: high — the label absence was confirmed in the workflow logs and by enumerating the repo's label set.

Proposed change

Create the ready-for-review label in the repository: gh label create 'ready-for-review' --repo redhat-developer/rhdh-plugin-export-overlays --description 'Code agent finished — ready for review agent' --color '0E8A16'. This is a stopgap until the upstream post-code.sh fix (agents#509) lands to auto-create missing labels.

Validation criteria

After the label is created, the next code agent PR should have the ready-for-review label successfully applied by the post-code script (no ##[warning]Failed to apply ready-for-review label in the workflow logs), and the review agent should be auto-dispatched without requiring a manual /fs-review command.

Generated by retro agent from https://github.com/redhat-developer/rhdh-plugin-export-overlays/pull/3045

Dominant language
TypeScript
Stars
9
Forks
72
Avg merge
3d 9h
Merged PRs (30d)
133

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redhat-developer/rhdh-plugin-export-overlays

All issues in redhat-developer/rhdh-plugin-export-overlays

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.