gganga-300/explain-github-issuev0.0.1Public
Explain github issue
Fetches a single GitHub issue by owner/repo/number and presents a structured digest for plain-English explanation
Before you run it1 service
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○GitHub
Code repository management and collaboration - issues, pull requests, commits, releases, code review
Inputs3, all required
rote asks for these before running and shows the defaults it will use.
- Owner
ownerGitHub repository owner
requiredstringcustom value allowed - Repo
repoGitHub repository name
requiredstringcustom value allowed - Issue number
issue_numberGitHub issue number
requiredintegercustom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- ServicesGitHub
- Adapters
githubmodiqo/github@0.0.2 resolved - Auth preflightBefore any service call, rote verifies every required local credential. Plan: declared as typed adapter.auth.ensure steps.
- Auth steps
auth_githubadapter/githubmissing → authorizeexpired → refreshunreadable → reauthorize - Digest
sha256:a4c505d3a73206ecd3e0fe47925a8beefb7a0c5bb87a5e6477464443c650b10f - Archive size2599 bytes
- Published2026-09-01T09:43:39.752374+00:00
- Published withrote 0.77.0
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.