Open PR — issue-111: add forgejo actions tools #122

New issue

Closed

opened 2026-08-29 03:29:42 +00:00 by david · 1 comment

david commented

2026-08-29 03:29:42 +00:00

Owner

Summary

Open the feature pull request issue-111: add forgejo actions tools (tracking issue #111) with body Closes #111. Merging is the repo owner's decision — never merge on own initiative.

Background

Part of the Forgejo Actions tooling feature (tracking issue #111 — branch feature/issue-111/forgejo-actions-tools). Depends on the final review (#121). Final step of Phase 8. The repo's AGENTS.md conventions: PRs are squash-merged and the source branch deleted when the owner merges; agents open the PR and ask whether to merge (the prompt is skipped when merging was already requested explicitly; non-interactive pi --print runs stop at the PR).

Implementation Details

Ensure the branch feature/issue-111/forgejo-actions-tools is pushed with commits prefixed issue-111: .
Open the PR against the default base branch (main) with:
- Title: issue-111: add forgejo actions tools
- Body: Closes #111 plus a concise summary of what shipped (5 tools, cache, docs) and the manual-validation note (Forgejo v16+ instance required).
Do NOT merge. Ask the repo owner whether to merge (squash + delete branch), unless merging was already requested explicitly.

Acceptance Criteria

PR is open with title issue-111: add forgejo actions tools and body containing Closes #111.
Branch follows feature/issue-111/forgejo-actions-tools; commits prefixed issue-111: .
PR is not merged by the implementer; merge decision explicitly handed to the repo owner.

Test Plan

View the PR in the web UI: title, body, Closes #111 link, changed-files list (src/actions.ts, src/actionsCache.ts, tests, README.md, DESIGN.md).
Confirm the tracking issue #111 shows the PR as closing reference.

### Summary Open the feature pull request `issue-111: add forgejo actions tools` (tracking issue **#111**) with body `Closes #111`. **Merging is the repo owner's decision** — never merge on own initiative. ### Background Part of the Forgejo Actions tooling feature (tracking issue **#111** — branch `feature/issue-111/forgejo-actions-tools`). Depends on the final review (**#121**). Final step of Phase 8. The repo's AGENTS.md conventions: PRs are squash-merged and the source branch deleted when the owner merges; agents open the PR and *ask* whether to merge (the prompt is skipped when merging was already requested explicitly; non-interactive `pi --print` runs stop at the PR). ### Implementation Details - Ensure the branch `feature/issue-111/forgejo-actions-tools` is pushed with commits prefixed `issue-111: `. - Open the PR against the default base branch (main) with: - Title: `issue-111: add forgejo actions tools` - Body: `Closes #111` plus a concise summary of what shipped (5 tools, cache, docs) and the manual-validation note (Forgejo v16+ instance required). - Do **NOT** merge. Ask the repo owner whether to merge (squash + delete branch), unless merging was already requested explicitly. ### Acceptance Criteria - [ ] PR is open with title `issue-111: add forgejo actions tools` and body containing `Closes #111`. - [ ] Branch follows `feature/issue-111/forgejo-actions-tools`; commits prefixed `issue-111: `. - [ ] PR is **not** merged by the implementer; merge decision explicitly handed to the repo owner. ### Test Plan - View the PR in the web UI: title, body, `Closes #111` link, changed-files list (src/actions.ts, src/actionsCache.ts, tests, README.md, DESIGN.md). - Confirm the tracking issue #111 shows the PR as closing reference.

david added this to the M7 - Actions documentation (last step) milestone

2026-08-29 03:29:42 +00:00

david added the

feature

label

2026-08-29 03:29:42 +00:00

david removed the

feature

label

2026-09-14 23:23:03 +00:00

david commented

2026-09-18 06:44:46 +00:00

Author

Owner

Closing as superseded — no consolidated PR is needed or possible.

The original plan (one feature branch feature/issue-111/forgejo-actions-tools → one PR closing #111) was not followed: each step issue (#112–#121) landed via its own PR, all merged into main:

#124 — zip-extraction dependency (issue-112)
#125 — src/actionsCache.ts cache module (issue-113)
#126 — metadata queries in src/actions.ts (issue-114)
#127 — job-log download (issue-115)
#128 — run-logs ZIP download (issue-116)
plus tool registration (#117), tests (#118), README.md (#119), DESIGN.md (#120), and final review (#121)

The full deliverable is already in main: extensions/forgejo/src/actions.ts, src/actionsCache.ts, both test suites, 5 forgejo_action_* tools registered in src/index.ts, and README/DESIGN docs. Tracking issue #111 is closed. The branch feature/issue-111/forgejo-actions-tools was never pushed, and no PR titled issue-111: add forgejo actions tools exists (verified against all 138 PRs).

Nothing remains to open or merge; the merge-decision handoff is moot.

Closing as superseded — no consolidated PR is needed or possible. The original plan (one feature branch `feature/issue-111/forgejo-actions-tools` → one PR closing #111) was not followed: each step issue (#112–#121) landed via its own PR, all merged into main: - #124 — zip-extraction dependency (issue-112) - #125 — `src/actionsCache.ts` cache module (issue-113) - #126 — metadata queries in `src/actions.ts` (issue-114) - #127 — job-log download (issue-115) - #128 — run-logs ZIP download (issue-116) - plus tool registration (#117), tests (#118), README.md (#119), DESIGN.md (#120), and final review (#121) The full deliverable is already in main: `extensions/forgejo/src/actions.ts`, `src/actionsCache.ts`, both test suites, 5 `forgejo_action_*` tools registered in `src/index.ts`, and README/DESIGN docs. Tracking issue #111 is closed. The branch `feature/issue-111/forgejo-actions-tools` was never pushed, and no PR titled `issue-111: add forgejo actions tools` exists (verified against all 138 PRs). Nothing remains to open or merge; the merge-decision handoff is moot.

david closed this issue

2026-09-18 06:44:48 +00:00