Skip to content

docs(tutorial): ticket-to-PR autonomous agent pipeline - #1335

Open
ekline[bot] wants to merge 1 commit into
mainfrom
docs/tutorial/agent-ticket-to-pr
Open

docs(tutorial): ticket-to-PR autonomous agent pipeline#1335
ekline[bot] wants to merge 1 commit into
mainfrom
docs/tutorial/agent-ticket-to-pr

Conversation

@ekline

@ekline ekline Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Context

This tutorial addresses a gap identified through competitor analysis, persona-needs assessment, and a feature-coverage audit of the Okteto docs. The docs landing page positions Okteto as "the environment platform for agentic development," and src/content/agentic/ documents the concepts — but no hands-on tutorial existed for the autonomous ticket-to-PR workflow, even though okteto/okteto-agent-skills ships a complete reference pipeline (examples/ticket-to-pr.yml) that the docs never linked to.

Top 3 gaps found

Rank Priority Gap Source Personas Type
1 High No hands-on tutorial for agentic workflows; agentic/ is all explanation, and the maintained ticket-to-pr.yml reference pipeline is never surfaced Competitor (Signadot ships 3 closed-loop agent tutorials; 7/8 competitors document AI agents) + product positioning + feature-without-guide Software Engineer, AI coding agents, Platform Engineer Tutorial
2 High Okteto Test has no standalone CI-integration guide; the okteto/test action appears only inside the Preview Environments tutorial Competitor (Signadot "tests in CI", Qovery E2E-with-GitHub-Actions) + persona Software Engineer, Platform Engineer How-to
3 Medium No guide for data isolation across many ephemeral environments (Volume Snapshots + Divert are documented separately, never tied together) Competitor (Signadot data + message-queue isolation) Software Engineer, Platform Engineer How-to

What this PR adds

A new tutorial, Ticket to pull request with an autonomous agent (src/tutorials/agent-ticket-to-pr.mdx), that walks through wiring Claude Code + the Okteto plugin into a GitHub Actions pipeline: labeling an issue agent triggers a run that creates an isolated Namespace, deploys the environment, implements the change, runs the e2e test container, smoke-tests live endpoints, and opens a PR. Covers the agent label authorization gate, credentials, the OKTETO_ALLOW_AGENT_DESTROY teardown policy, namespace isolation, security considerations, and troubleshooting. Registered in sidebarTutorials.js (third, after the two getting-started tutorials) and cross-linked from agentic/autonomous-workflows.mdx.

Serves the Software Engineer and Platform Engineer personas, and the AI-coding-agent readership (exact, complete commands; explicit prerequisites and destructive-behavior callouts).

Research sources

  • Competitor audit of 8 products (Coder, Ona, Qovery, Orca, Paseo, herdr, Signadot, Telepresence): 7/8 document AI agent integration; Signadot ships three "closed-loop verification" tutorials (Claude Code, Cursor, Codex) and has repositioned its homepage around exactly this pattern — the workflow Okteto had no tutorial for.
  • Grounded entirely in verified upstream sources: okteto/okteto-agent-skills (examples/ticket-to-pr.yml, examples/README.md, plugins/okteto/hooks/guard-okteto.sh, plugins/okteto/skills/okteto/SKILL.md) and okteto/movies (okteto.yaml).

Remaining gaps (follow-up)

How to verify

  1. cd docs && yarn && yarn build — validates links and anchors (onBrokenLinks/onBrokenAnchors are set to throw).
  2. yarn start, open /docs/tutorials/agent-ticket-to-pr/, and confirm the page renders, appears third in the Tutorials sidebar with the Claude logo, and that the cross-link from Autonomous Workflows resolves.
  3. Optionally follow the tutorial end to end against a real Okteto instance: fork okteto/movies, add the workflow, label an issue agent, and confirm a tested PR is opened.

Note for reviewers: yarn build was NOT run in the authoring environment (Node/yarn unavailable there). Links and anchors were validated by hand against version-1.47 targets, but please run the build in CI/locally to confirm.

Please also review two workspace-config drift items I noticed (out of scope for this PR, flagged for awareness): the repo CLAUDE.md still says lastVersion is 1.43/next 1.44 (actual: 1.47/1.48) and lists src/content/okteto-ai/, which no longer exists (removed in #1317).

ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>


📝 Created with EkLine · View session

Add a hands-on tutorial for the autonomous agentic workflow: wiring
Claude Code and the Okteto plugin into a GitHub Actions pipeline so a
labeled issue produces a tested pull request against a live Okteto
environment. Register it in the tutorials sidebar and cross-link it
from the Autonomous Workflows page.

ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>

Signed-off-by: ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>
@netlify

netlify Bot commented Aug 26, 2026

Copy link
Copy Markdown

Deploy Preview for okteto-docs ready!

Name Link
🔨 Latest commit 78ecb6e
🔍 Latest deploy log https://app.netlify.com/projects/okteto-docs/deploys/6a8ebdc53450a50008f3deff
😎 Deploy Preview https://deploy-preview-1335--okteto-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@ekline
ekline Bot requested a review from rberrelleza August 26, 2026 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants