50 lines
2.9 KiB
Markdown
50 lines
2.9 KiB
Markdown
---
|
|
name: gitea
|
|
description: Provides information and workflows for interacting with Gitea.
|
|
license: MIT
|
|
compatibility: opencode
|
|
metadata:
|
|
audience: agents
|
|
workflow: gitea-development
|
|
---
|
|
|
|
## What Gitea is
|
|
Gitea is a self-hosted Git service that is very similar to GitHub.
|
|
|
|
## Important Notes
|
|
- **Do NOT use gitea.com**: We self-host Gitea at `git.nubo.sh`.
|
|
- **Workflow**: The workflow is much the same as GitHub (issues, PRs, etc.).
|
|
|
|
## How to use the `tea` CLI
|
|
Use the `tea` command to interact with Gitea.
|
|
- `tea notifications`: Check for new notifications.
|
|
- `tea issue <number>`: Read an issue.
|
|
- `tea issue --comments <number>`: Read an issue and its comments.
|
|
- `tea comment <number> "message"`: Comment on an issue.
|
|
- `tea pulls`: Manage pull requests.
|
|
- `tea pulls create`: Create a pull request.
|
|
- `tea pulls <number>`: Read a pull request (e.g., `tea pulls 6`).
|
|
- `tea pulls --comments <number>`: Read a pull request and its comments.
|
|
- **Marking as Read**: Use `tea notifications read` to mark notifications as read.
|
|
- **When to mark as read**: Only mark notifications as read once you have actively addressed the underlying task or review.
|
|
|
|
## Development Workflows
|
|
- **Issues**: Use `tea issue` to track tasks and bugs. Before closing an issue, ensure the relevant Pull Request has been merged.
|
|
- **Pull Requests**: Use `tea pulls` to manage and review code changes.
|
|
- **Communication**: Use `tea comment <number> "message"` to communicate with project maintainers (e.g., `@hulthe`).
|
|
|
|
## Responsibility
|
|
- **Don't Drop the Ball**: When assigned a task or receiving a review comment, you MUST address it before moving on to other things. Ensure all follow-up actions (like replying to a comment) are completed.
|
|
|
|
## Tips for Agents
|
|
- **Stay Updated**: Regularly run `tea notifications` to check for new issues or PR reviews.
|
|
- **Communicate**: If confused, use `tea comment <number> "message"` and mention the maintainer (e.g., `@hulthe`).
|
|
- **Clean History**: Use `git rebase` and squash commits before submitting a PR to keep the history clean.
|
|
- **Use Tea**: Use the `tea` CLI for a faster, terminal-based workflow.
|
|
- **Explicitly Ping**: When replying to a comment, use the `@` sign to explicitly ping or mention the person you are replying to. This ensures they receive a notification.
|
|
- **CI / Actions**: Gitea uses `.gitea/workflows/` (not `.github/`). Use `tea actions runs` to list runs; `tea actions runs logs <id>` to inspect. A `Status: completed` does NOT mean success — always read the log tail for `Job succeeded` or `Job failed`. The Alpine runner requires `node` before `actions/checkout` and uses package names `rust-clippy` / `rustfmt` (not `clippy`).
|
|
|
|
## Assignment
|
|
- **Tracking Assignments**: Use `tea issue --assignee <your-username>` to see issues assigned to you. Also use `tea pulls --assignee <your-username>` for pull requests.
|
|
- **Checking Work**: Regularly check your notifications and assigned issues to ensure you are up to date with your tasks.
|