feat: MCP resource templates — 7 entities on forgejo:// URI scheme #172
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!172
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/172/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Implements all 7 slices of the OpenSpec change
mcp-resource-templates(proposed in #148, merged 2026-05-28). Adds 7 URI-addressable MCP resources alongside the existing tool surface.forgejo://owner/{owner}forgejo://repo/{owner}/{repo}forgejo://repo/{owner}/{repo}/commit/{sha}forgejo://repo/{owner}/{repo}/commit/{sha}/statusget_commit_statuses).forgejo://repo/{owner}/{repo}/issue/{index}list_issue_comments).forgejo://repo/{owner}/{repo}/{kind}/{index}/comment/{id}kind ∈ {issue, pr}.forgejo://repo/{owner}/{repo}/pr/{index}Coexists with the existing tool surface — no tool removed. Embedded lists capped at 30 items with a truncation sentinel naming the corresponding
list_*tool.Why
Per design.md D1, D5, D6, D8, D9: instance-portable URI scheme, read-on-demand only (
subscribe=false, listChanged=falsefor v1), per-domainRegisterXResourcespattern mirroring existingRegisterXTool, embedded-list bounding satisfiesdocs/design/output-bounding.mdwithout a new query param onresources/read, JSON primary + markdown sidecar for entities carrying rendered text.Driven by bead
forgejo-mcp-13x.Implementation
Built via
team:dev-loop(impl + runner). One impl replacement mid-flight after the original ignored two checkpoint probes — clean handoff via worktree state, no work lost.Commits:
4249374slices 1+2: core framework (operation/resource/package: parse, bound, errors, register) + commit resource52b19acslice 3: commit status resource (aggregate state computed client-side)79d0940slices 4+5: repo + owner resources, issue + comment resources,-32602invalid-params mappingf6cc2f1slices 6+7: PR resource, README/AGENTS.md enriched, CHANGELOG entry, follow-up beads filedNew code:
operation/resource/— 4 source files + 3 test files (URI parsing, bounding, error mapping)operation/repo/resources_{commit,status,repo}.go+ testsoperation/user/resources_owner.go+ testsoperation/issue/resources.go+ testsoperation/pull/resources.go+ testsoperation/operation.goextended withserver.WithResourceCapabilities(false, false)+RegisterCoreResourcesNet: ~2400 LOC added across 21 files.
OpenSpec status
46/47 tasks ticked in
openspec/changes/mcp-resource-templates/tasks.md. Task 1.11 (manual client verification across Claude Code, Claude Desktop, Codex, Cursor) remains — out of scope for the implementation team; will be exercised post-merge against a real MCP client.Follow-ups filed:
forgejo-mcp-7rarevisitWithResourceCapabilities(subscribe=true, …)once a real subscription use case appearsforgejo-mcp-7derevisitEmbeddedListCap=30once usage telemetry availableOut of Scope
resources/subscribe(tracked inforgejo-mcp-7ra)Test Plan
go build ./...cleango test -count=1 ./...green (verified byrunnerafter every slice; lead independent re-runs after each push)operation/resource/PASS lines ≥ 21operation/repo≥ 9,operation/user≥ 4,operation/issue≥ 6,operation/pull≥ 6openspec validate --all --strict(Tekton openspec-validate gate confirms)Closes the implementation portion of
forgejo-mcp-13x.op1st Pipelines as Code/openspec-validate-pr-pwkpp is running.
Starting Pipelinerun openspec-validate-pr-pwkpp in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-pwkpp -fop1st Pipelines as Code/on-pull-request-2qvgz is running.
Starting Pipelinerun on-pull-request-2qvgz in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-2qvgz -fop1st Pipelines as Code/code-scans-dfz5d is running.
Starting Pipelinerun code-scans-dfz5d in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-dfz5d -fop1st Pipelines as Code/code-scans-dfz5d has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-pwkpp has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/on-pull-request-2qvgz has failed.
Task Statuses:
fetch-source
commit-title-check
build-and-test
Failure snippet:
task build-and-test has the status "Failed":op1st Pipelines as Code/openspec-validate-pr-mgvsw is running.
Starting Pipelinerun openspec-validate-pr-mgvsw in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-mgvsw -fop1st Pipelines as Code/code-scans-rhbv6 is running.
Starting Pipelinerun code-scans-rhbv6 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-rhbv6 -fop1st Pipelines as Code/on-pull-request-dph52 is running.
Starting Pipelinerun on-pull-request-dph52 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-dph52 -fop1st Pipelines as Code/code-scans-rhbv6 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-mgvsw has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/on-pull-request-dph52 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/code-scans-gjkpc is running.
Starting Pipelinerun code-scans-gjkpc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-gjkpc -fop1st Pipelines as Code/openspec-validate-pr-d484f is running.
Starting Pipelinerun openspec-validate-pr-d484f in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-d484f -fop1st Pipelines as Code/on-pull-request-5bpn8 is running.
Starting Pipelinerun on-pull-request-5bpn8 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-5bpn8 -fack review finding on
operation/pull/resources.go:79(typo) — fixed in683404c. Beadforgejo-mcp-8iaclosed.op1st Pipelines as Code/openspec-validate-pr-d484f has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/code-scans-zb49s is running.
Starting Pipelinerun code-scans-zb49s in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-zb49s -fop1st Pipelines as Code/openspec-validate-pr-nlcpj is running.
Starting Pipelinerun openspec-validate-pr-nlcpj in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-nlcpj -fop1st Pipelines as Code/on-pull-request-lplhn is running.
Starting Pipelinerun on-pull-request-lplhn in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-lplhn -fop1st Pipelines as Code/on-pull-request-5bpn8
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "TaskRunCancelled":op1st Pipelines as Code/code-scans-gjkpc
Task Statuses:
fetch-source
gitleaks-version
gitleaks
Failure snippet:
task gitleaks has the status "TaskRunCancelled":op1st Pipelines as Code/code-scans-gjkpc
Task Statuses:
fetch-source
gitleaks-version
gitleaks
Failure snippet:
task gitleaks has the status "TaskRunCancelled":ack review finding on
operation/repo/resources_commit.go:51(double-wrapped ResourceError) — fixed inf8d661e. Beadforgejo-mcp-cmwclosed.op1st Pipelines as Code/code-scans-zb49s has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-nlcpj has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/code-scans-rrth9 is running.
Starting Pipelinerun code-scans-rrth9 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-rrth9 -fop1st Pipelines as Code/openspec-validate-pr-4tdz9 is running.
Starting Pipelinerun openspec-validate-pr-4tdz9 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-4tdz9 -fop1st Pipelines as Code/on-pull-request-67tqg is running.
Starting Pipelinerun on-pull-request-67tqg in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-67tqg -fop1st Pipelines as Code/on-pull-request-lplhn
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "TaskRunCancelled":ack review finding on
operation/resource/parse.go:220(splitPath empty/whitespace segments) — fixed in55a39f4. Rejection centralized inparseForgejoURI; double-slash, trailing slash, and %-encoded whitespace now return -32602 invalid-params instead of aliasing onto canonical URIs. Beadforgejo-mcp-16tclosed.op1st Pipelines as Code/openspec-validate-pr-4tdz9 has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/code-scans-rrth9 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/on-pull-request-67tqg has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/code-scans-dz79x is running.
Starting Pipelinerun code-scans-dz79x in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-dz79x -fop1st Pipelines as Code/openspec-validate-pr-bc25m is running.
Starting Pipelinerun openspec-validate-pr-bc25m in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-bc25m -fop1st Pipelines as Code/on-pull-request-h2j4c is running.
Starting Pipelinerun on-pull-request-h2j4c in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-h2j4c -fack review finding on
operation/repo/resources_commit.go:39(parse error not mapped) — fixed in81d1945. Handler now routes parse errors throughresource.MapForgejoError, matching issue/pr handlers. Currently surfaces as-32603untilforgejo-mcp-wgslifts unrecognized parse-error strings to-32602. Beadforgejo-mcp-vzzclosed.op1st Pipelines as Code/code-scans-dz79x has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-bc25m has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/code-scans-7hm4x is running.
Starting Pipelinerun code-scans-7hm4x in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-7hm4x -fop1st Pipelines as Code/openspec-validate-pr-6q4fj is running.
Starting Pipelinerun openspec-validate-pr-6q4fj in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-6q4fj -fop1st Pipelines as Code/on-pull-request-c9b8s is running.
Starting Pipelinerun on-pull-request-c9b8s in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-c9b8s -fack review finding on
operation/repo/resources_repo.go:61(parse error not mapped) — fixed in0c177af. Same pattern as81d1945. Beadforgejo-mcp-s2gclosed.op1st Pipelines as Code/on-pull-request-h2j4c
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "TaskRunCancelled":op1st Pipelines as Code/openspec-validate-pr-6q4fj has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/code-scans-7hm4x has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-xqq7s is running.
Starting Pipelinerun openspec-validate-pr-xqq7s in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-xqq7s -fop1st Pipelines as Code/code-scans-zslt4 is running.
Starting Pipelinerun code-scans-zslt4 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-zslt4 -fop1st Pipelines as Code/on-pull-request- has failed.
There was an error creating the PipelineRun: on-pull-request-
cannot use the API on the provider platform to create a in_progress status:
ack review finding on
operation/repo/resources_status.go:65(parse error not mapped) — fixed in10c8403. Beadforgejo-mcp-g5sclosed.op1st Pipelines as Code/openspec-validate-pr- has failed.
There was an error creating the PipelineRun: openspec-validate-pr-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 33 comments in 10 minutes: rate limited
op1st Pipelines as Code/on-pull-request- has failed.
There was an error creating the PipelineRun: on-pull-request-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 33 comments in 10 minutes: rate limited
op1st Pipelines as Code/code-scans- has failed.
There was an error creating the PipelineRun: code-scans-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 33 comments in 10 minutes: rate limited
ack review finding on
operation/user/resources_owner.go:56(parse error not mapped) — fixed in6cecf67. Last commit in the parse-error mapping cluster (vzz/s2g/g5s/iqi). Beadforgejo-mcp-iqiclosed.op1st Pipelines as Code/openspec-validate-pr-59vjg is running.
Starting Pipelinerun openspec-validate-pr-59vjg in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-59vjg -fop1st Pipelines as Code/code-scans-zwqzd is running.
Starting Pipelinerun code-scans-zwqzd in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-zwqzd -fop1st Pipelines as Code/on-pull-request-57krl is running.
Starting Pipelinerun on-pull-request-57krl in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-57krl -fack review finding on
operation/resource/errors.go:26(substring HTTP classification + parse-error -32602 gap) — fixed in1aa797a. Introducedresource.ErrInvalidParamssentinel; all parser error paths wrap it;MapForgejoErrornow useserrors.Is(err, ErrInvalidParams)for -32602 before the 403/404 substring fallback. Parser errors no longer fall through to -32603. Beadforgejo-mcp-wgsclosed.op1st Pipelines as Code/code-scans-zwqzd has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-59vjg has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/on-pull-request-57krl has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/on-pull-request-bjx6w is running.
Starting Pipelinerun on-pull-request-bjx6w in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-bjx6w -fop1st Pipelines as Code/code-scans-qbv6b is running.
Starting Pipelinerun code-scans-qbv6b in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-qbv6b -fop1st Pipelines as Code/openspec-validate-pr-w7pmj is running.
Starting Pipelinerun openspec-validate-pr-w7pmj in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-w7pmj -fack review finding on
operation/user/resources_owner.go:96(user→org fallback masking + nil-userErr edge) — fixed in19f1efd. Reordered: both-404 check first → explicit-32003; non-404 HTTP error → status-enriched; transport (nil resp) error →orgErrsurfaced (no longer masked by user 404). Three new test cases. Beadforgejo-mcp-91jclosed.op1st Pipelines as Code/code-scans-qbv6b has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-w7pmj has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/on-pull-request-bjx6w has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/openspec-validate-pr-hbpt7 is running.
Starting Pipelinerun openspec-validate-pr-hbpt7 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-hbpt7 -fop1st Pipelines as Code/code-scans-n626g is running.
Starting Pipelinerun code-scans-n626g in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-n626g -fop1st Pipelines as Code/on-pull-request-5gqqq is running.
Starting Pipelinerun on-pull-request-5gqqq in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-5gqqq -fack review finding on
operation/repo/resources_status.go:73(ListStatuses no PageSize) — fixed inee1217d. Now requestsEmbeddedListCap+1soBoundedcan distinguish at-cap from over-cap. Beadforgejo-mcp-827closed.op1st Pipelines as Code/code-scans-n626g has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-hbpt7 has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/openspec-validate-pr-ppmsd is running.
Starting Pipelinerun openspec-validate-pr-ppmsd in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-ppmsd -fop1st Pipelines as Code/code-scans-dm4p6 is running.
Starting Pipelinerun code-scans-dm4p6 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-dm4p6 -fop1st Pipelines as Code/on-pull-request- has failed.
There was an error creating the PipelineRun: on-pull-request-
cannot use the API on the provider platform to create a in_progress status:
op1st Pipelines as Code/on-pull-request-5gqqq
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "TaskRunCancelled":ack review finding on
operation/issue/resources.go:93(ListIssueComments default PageSize) — fixed in321b1a0. Same pattern asee1217d. Beadforgejo-mcp-u3yclosed.op1st Pipelines as Code/openspec-validate-pr-ppmsd has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/code-scans-dm4p6 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/code-scans-qttnc is running.
Starting Pipelinerun code-scans-qttnc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-qttnc -fop1st Pipelines as Code/on-pull-request-bv48q is running.
Starting Pipelinerun on-pull-request-bv48q in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-bv48q -fop1st Pipelines as Code/openspec-validate-pr- has failed.
There was an error creating the PipelineRun: openspec-validate-pr-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 61 comments in 30 minutes: rate limited
ack review finding on
operation/pull/resources.go:108(ListIssueComments default PageSize) — fixed in9e5b930. Beadforgejo-mcp-ghrclosed.op1st Pipelines as Code/openspec-validate-pr- has failed.
There was an error creating the PipelineRun: openspec-validate-pr-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 62 comments in 30 minutes: rate limited
op1st Pipelines as Code/code-scans- has failed.
There was an error creating the PipelineRun: code-scans-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 62 comments in 30 minutes: rate limited
op1st Pipelines as Code/on-pull-request- has failed.
There was an error creating the PipelineRun: on-pull-request-
cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 63 comments in 30 minutes: rate limited
ack review finding on
operation/pull/resources.go:111(ListPullReviews default PageSize) — fixed in182898a. Beadforgejo-mcp-5dzclosed.All 13 review findings addressed. Umbrella bead
forgejo-mcp-ylb(fix-pull_172) closes with this commit.Fix-chain summary:
683404cCommmentsTruncated→CommentsTruncatedf8d661e*ResourceErrorin commit handler55a39f481d1945MapForgejoError0c177afMapForgejoError10c8403MapForgejoError6cecf67MapForgejoError1aa797aErrInvalidParamssentinel →-32602for all parser errors19f1efdorgErron transport failure, explicit-32003on both-404ee1217dListStatusesPageSize=cap+1321b1a0ListIssueComments(issue) PageSize=cap+19e5b930ListIssueComments(pr) PageSize=cap+1182898aListPullReviewsPageSize=cap+1/test
op1st Pipelines as Code/on-pull-request-wj2x2 is running.
Starting Pipelinerun on-pull-request-wj2x2 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-wj2x2 -fop1st Pipelines as Code/openspec-validate-pr-nswgc is running.
Starting Pipelinerun openspec-validate-pr-nswgc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-nswgc -fop1st Pipelines as Code/code-scans- has failed.
There was an error creating the PipelineRun: code-scans-
cannot use the API on the provider platform to create a in_progress status:
op1st Pipelines as Code/openspec-validate-pr-nswgc has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/on-pull-request-wj2x2 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
/test code-scans
op1st Pipelines as Code has failed.
There was an issue validating the commit: "error getting remote task from pipelinerun annotations: annotations in pipeline are in wrong format: [git-clone,\n .tekton/release-tools/tasks/build-image.yaml,\n .tekton/release-tools/tasks/verify-image-tools.yaml,\n .tekton/release-tools/tasks/syft-scan-image.yaml]"
ack PaC validation failure (comment 16027445) — fixed in
3a12931.Root cause:
.tekton/release-tools-on-pull-request-build.yamland.tekton/release-tools-on-tag-publish.yamldeclared thepipelinesascode.tekton.dev/taskannotation as a folded scalar (>-) with continuation lines indented one space deeper than the opening[git-clone,. YAML 1.2 preserves newlines under that indent pattern (line-more-indented rule), so PaC saw a literal multi-line string. Collapsed both to single-line inline lists; verified with yq.Bead
forgejo-mcp-wbwclosed.op1st Pipelines as Code/openspec-validate-pr-98j8r is running.
Starting Pipelinerun openspec-validate-pr-98j8r in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines openspec-validate-pr-98j8r -fop1st Pipelines as Code/code-scans-xfxkn is running.
Starting Pipelinerun code-scans-xfxkn in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-xfxkn -fop1st Pipelines as Code/on-pull-request-ddzdw is running.
Starting Pipelinerun on-pull-request-ddzdw in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-ddzdw -fop1st Pipelines as Code/code-scans-xfxkn has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/openspec-validate-pr-98j8r has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/on-pull-request-ddzdw has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
Merged. Head branch
worktree-mcp-resources-coredeleted.Closes implementation portion of
forgejo-mcp-13x. Follow-ups remain open:forgejo-mcp-7ra— revisitWithResourceCapabilities(subscribe=true)once real subscription use case appearsforgejo-mcp-7de— revisitEmbeddedListCap=30once usage telemetry available