Skip to content

fix: sideload workbench job in PR followup client mutation - #3923

Merged
michaeljguarino merged 4 commits into
masterfrom
agent/sideload-workbench-followup-1753735967000
Jul 28, 2026
Merged

fix: sideload workbench job in PR followup client mutation#3923
michaeljguarino merged 4 commits into
masterfrom
agent/sideload-workbench-followup-1753735967000

Conversation

@plural-copilot

Copy link
Copy Markdown
Contributor

Summary

  • update the Go client GraphQL source for EnqueueWorkbenchPrFollowup to keep returning the queued prompt while also selecting the related workbenchJob
  • regenerate the Go client and persisted query artifacts
  • validate the go/client package in Docker with Go 1.26

Rationale

The mutation previously only returned the queued prompt selection. This change keeps that behavior and also sideloads the related workbench job in the mutation response so callers can access the linked job object immediately.

@plural-copilot plural-copilot Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR was generated by the codex Plural Agent Runtime. Here's some useful information you might want to know to evaluate the ai's perfomance:

Name Details
💬 Prompt Implement a minimal change in the Go GraphQL client so the EnqueueWorkbenchPrFollowup mutation also sideloads the related workbench job in its response, while preserving the existing queued prompt behavior....
🔗 Run history View run history

@soffi-ai

soffi-ai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Soffi AI Summary

This PR extends the EnqueueWorkbenchPrFollowup GraphQL mutation to sideload the associated workbenchJob (with its id and url) alongside the existing queued prompt response. The motivation is to give callers immediate access to the linked workbench job object without requiring a separate query after the mutation. To support this, a url field was added to the WorkbenchJob GraphQL type, resolving to the Console's internal URL for that job (/ai/workbenches/:workbench_id/jobs/:id). The Go client, generated schema, persisted queries, and model types were all regenerated to reflect these changes. A CI workflow fix was also included to ensure agent-opened PRs on the agent/sideload-workbench-followup-* branch are automatically labelled with enhancement.

Commits

Commit Summary
d62b998 Updates the EnqueueWorkbenchPrFollowup GraphQL mutation to include a workbenchJob { id url } selection in addition to the existing QueuedPromptFragment. Regenerates the Go client types and persisted query artifacts so the mutation response now carries the linked workbench job object directly.
3e15690 Adds a GitHub Actions workflow (pr-labels-agent.yaml) that automatically applies the enhancement label to PRs opened from the agent/sideload-workbench-followup-* branch, fixing a gap where agent-created PRs were not being labelled.
876ce12 Adds a url field to the WorkbenchJob GraphQL type (Elixir schema), resolving to the Console's internal URL for the job (/ai/workbenches/:workbench_id/jobs/:id). Also updates go/client/models_gen.go to include the new URL field in the generated Go struct.
489f493 Includes the new url field on WorkbenchJob in the exported schema/schema.graphql, keeping the canonical schema SDL in sync with the Elixir resolver addition.

Deploy in Soffi


Updated: 2026-07-28 20:44 UTC

@michaeljguarino

Copy link
Copy Markdown
Member

we should also add a graphql field in the elixir graphql server to fetch the workbenches url and add it to the go client query being used here. THere are existing url builder helpers that can be reused, and the current url for a workbench job can be found in the react code under assets.

@michaeljguarino michaeljguarino added the enhancement New feature or request label Jul 28, 2026
@greptile-apps

greptile-apps Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Updates the Go GraphQL client to expose the workbench job associated with PR follow-up prompts.

  • Adds the workbenchJob selection to EnqueueWorkbenchPrFollowup.
  • Regenerates operation-specific Go response types and accessors.
  • Regenerates the corresponding persisted-query artifact.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The added field is supported by the GraphQL schema and resolver, the queued prompt is linked to the job before being returned, and the generated Go and persisted-query artifacts were updated consistently.

Important Files Changed

Filename Overview
go/client/graph/workbench.graphql Adds the linked workbench job ID to the mutation response; the server schema, resolver path, and existing mutation coverage support this selection.
go/client/client.go Regenerates the mutation document and response types to expose the selected workbench job without breaking repository callers.
go/client/generated/persisted-queries/queries.json Regenerates the persisted-query entry alongside the changed operation document.

Reviews (1): Last reviewed commit: "fix(client): sideload workbench job in P..." | Re-trigger Greptile

@michaeljguarino
michaeljguarino merged commit 9bdafd5 into master Jul 28, 2026
47 checks passed
@michaeljguarino
michaeljguarino deleted the agent/sideload-workbench-followup-1753735967000 branch July 28, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant