the signals and their derived score are provisional and subject to change.
validate manually before sharing.
44915d28a19d0504ace8b21b6eb5439c02cea16f9e493971a38c0aa35358f6ca90530ffebe667 months ago🤖 Generated with [Claude Code](https://claude.com/claude-code)fc81396870f77 months ago🤖 Generated with [Claude Code](https://claude.com/claude-code)76923a35d4d18 months ago🤖 Generated with [Claude Code](https://claude.com/claude-code)- Never assume, verify before claiming
- Development targets are in the `Makefile`; read `CONTRIBUTING.md` for the command style and package structure
- PR descriptions: minimal, only what and why, no task or file listings. Aim for less than 1000 characters
- Reference issues and PRs by full URL, not by number
- Use Conventional Commits for commit messages and PR titles (`build`, `chore`, `ci`, `docs`, `enhance`, `feat`, `fix`, `perf`, `refactor`, `revert`, `style`, `test`), with `enhance` for user-facing e---
name: gt
description: >-
Drives Gitea (gitea.com or self-hosted) through gt, the official Gitea CLI: checks whether a
pull request's CI passed and reads the logs of the jobs that failed, reruns Actions jobs,
reads an issue and opens a pull request for it, comments on issues and pull requests,
reviews with inline comments, merges, searches issues and pull requests, manages releases
and wiki pages, dispatches workflows, scripts gt in CI with GITEA_TOKEN, and makes raw Gitea
API calls with gt anone