mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-20 08:06:35 +03:00
36 lines
1.6 KiB
Markdown
36 lines
1.6 KiB
Markdown
# Forgejo CLI v2 — safe repository automation
|
|
|
|
Manage a Forgejo server from the terminal without hand-written `curl` or accidental mutations. It covers daily repository work—issues, pull requests, repositories, contents, metadata, webhooks, and settings—and has a guarded API escape hatch for the rest.
|
|
|
|
## Why Install This Skill
|
|
|
|
The CLI gives agents one predictable safety contract: JSON is machine-readable, diagnostics stay off stdout, mutations require confirmation, and dry runs never need a token or network access. For version-specific features such as Actions runners and variables, packages, organizations, teams, admin APIs, notifications, and permissions, use the generic API command with your server's Swagger schema.
|
|
|
|
## What You Get
|
|
|
|
| Contents | Purpose |
|
|
| --- | --- |
|
|
| `scripts/forgejo-cli` | Argparse Forgejo API v1 client |
|
|
| `references/command-reference.md` | Endpoint and payload guide |
|
|
| `V2-SPEC.md` | v2 acceptance criteria |
|
|
| `tests/` | Offline stdlib contract tests |
|
|
|
|
## Quick Start
|
|
|
|
Set `FORGEJO_AGENT_TOKEN` (default) or `FORGEJO_USER_TOKEN`, then run:
|
|
|
|
```bash
|
|
python3 scripts/forgejo-cli --dry-run --json repo create --name demo --private
|
|
python3 scripts/forgejo-cli --server https://forge.example api --method GET --path /api/v1/user --json
|
|
```
|
|
|
|
## Triggers
|
|
|
|
- Managing Forgejo/Gitea issues, PRs, repos, file contents, releases, or hooks.
|
|
- Calling a version-specific `/api/v1/` endpoint safely.
|
|
- Previewing a Forgejo mutation.
|
|
|
|
## Requirements
|
|
|
|
Python 3.8+ and `requests` for live API calls. `--help` and `--dry-run` need no token or dependency. Consult your Forgejo server's `/api/swagger` or `/swagger.v1.json` for exact schemas.
|