Using Gitea

Gitea as Your Second Brain's Notebook

Gitea isn't just for code. Its issue tracker is a powerful project management tool. You can use it to:

• Track tasks and ideas across multiple projects
• Break work into manageable pieces with checklists
• Link related issues with dependencies
• Have your OpenClaw read and create issues via the API
• Keep a searchable, organized record of decisions and plans

This lesson covers how to use Gitea's issue system effectively.

Start Simple

Here's a practical ramp-up so you don't build a system you'll abandon:

• Week 1: Just use issues. No labels, no milestones. Get comfortable creating and closing them.
• Week 2: Add 3–4 labels if you find yourself wanting to filter (e.g., priority:high, type:task).
• Week 3+: Add milestones only if you have actual deadlines or grouped goals.

Creating Repositories

A repository (repo) is a container for a project. Create one for each distinct area:

1. Click + → New Repository
2. Give it a name (e.g., home-projects, learning-notes, openclaw-config)
3. Check Initialize this repository (creates a README)
4. Click Create Repository

Some repo ideas:

• personal-tasks — general to-do tracking
• openclaw-config — version-controlled backup of your OpenClaw configuration
• learning — notes, curriculum tracking, book summaries
• A repo per major project you're working on

Issues: The Core Unit

An issue is a single trackable item — a task, a bug, an idea, a question.

Creating an Issue

1. Go to a repo → Issues tab → New Issue
2. Title: Clear, actionable ("Set up weekly grocery delivery" not "groceries")
3. Body: Use markdown for structure:

## What
Research and set up weekly grocery delivery service.

## Steps
- [ ] Compare Instacart vs. local co-op delivery
- [ ] Set up account with chosen service
- [ ] Create first weekly order template
- [ ] Schedule recurring delivery for Saturdays

## Notes
Budget: ~$150/week including delivery fee.

The - [ ] syntax creates checkboxes that you can tick off as you progress. Gitea shows a progress bar ("2 of 5 tasks") on the issue list.

Labels

Labels categorize issues. Create labels that make sense for your workflow:

1. Go to Issues → Labels → New Label
2. Useful starting labels:
   • priority:high (red) — do this first
   • priority:low (blue) — when you get to it
   • type:task (green) — something to do
   • type:idea (purple) — something to think about
   • type:bug (orange) — something broken
   • blocked (gray) — waiting on something else

Milestones

Milestones group issues toward a goal with an optional due date:

1. Issues → Milestones → New Milestone
2. Name it (e.g., "OpenClaw Fully Configured", "Q2 Projects")
3. Set a due date if relevant
4. Assign issues to the milestone

The milestone page shows a progress bar of open vs. closed issues — satisfying to watch fill up.

Comments: The Conversation

Every issue has a comment thread. Use comments to:

• Log progress: "Compared Instacart vs. co-op. Going with co-op — better prices, supports local."
• Record decisions: "Decided to go with Saturday delivery. Wednesday was too mid-week."
• Paste research: Links, quotes, screenshots
• Talk to your OpenClaw: If you connect Gitea to OpenClaw, it can comment on issues with research or analysis

Comments support full markdown — code blocks, images, links, tables.

Dependencies: Linking Related Issues

Gitea supports issue dependencies — "this issue blocks that issue" or "this issue depends on that issue."

Setting Dependencies

1. Open an issue
2. In the right sidebar, find Dependencies
3. Click Add dependency
4. Search for the blocking/blocked issue
5. Choose the relationship:
   • Depends on: This issue can't be done until the other is closed
   • Blocks: This issue is blocking the other from being done

Why This Matters

When you view an issue with unresolved dependencies, Gitea shows them prominently. You can't accidentally close a blocked issue without seeing the warning. This is powerful for:

• Multi-step projects where order matters
• Tasks that depend on external decisions
• Coordinating work across multiple repos

Cross-References

Mention other issues anywhere in Gitea by typing # followed by the issue number:

• #5 links to issue 5 in the same repo
• owner/repo#5 links to issue 5 in a different repo

When you reference an issue, it shows up in that issue's timeline. This creates a web of connected context.

Using Gitea with Your OpenClaw

Remember the API token you created in Lesson 16, Step 4? That's what allows OpenClaw to talk to your Gitea instance. If you skipped that step, go back and create one now.

With the token configured, your OpenClaw can interact with Gitea programmatically through Telegram.

Reading issues

Ask your OpenClaw: "What are the open issues in my personal-tasks repo?"

It calls the Gitea API:

GET /api/v1/repos/yourname/personal-tasks/issues?state=open

Creating issues

Tell your OpenClaw: "Create an issue in personal-tasks: Research solar panel installers. Label it priority:high."

It calls:

POST /api/v1/repos/yourname/personal-tasks/issues

Commenting on issues

"Add a comment to issue 12 in personal-tasks: Called three installers, best quote was $15k for 8kW system."

POST /api/v1/repos/yourname/personal-tasks/issues/12/comments

This turns your OpenClaw + Gitea into a conversational project management system. You talk to your assistant over Telegram, and the structured output lives in Gitea where you can review, search, and organize it.

Workflow Tips

Weekly Review

Once a week, spend 15 minutes:

1. Close completed issues
2. Review open issues — are they still relevant?
3. Check milestones — are you on track?
4. Create new issues for anything you've been carrying in your head

Capture Everything

The cost of an issue is nearly zero. If something crosses your mind, create an issue. You can always close it later. Better to have it tracked than to forget it.

Use Checklists for Multi-Step Tasks

The - [ ] checkbox syntax in issue bodies is ideal for tasks with clear steps. Gitea shows a progress bar ("2 of 5 tasks") on the issue list.

When You're Done

• Created at least one repository
• Created several issues with markdown bodies and checklists
• Set up a few labels
• Created a milestone
• Linked two issues with a dependency
• Used cross-references between issues
• Commented on an issue with a progress update
• (Optional) Had your OpenClaw read or create an issue via the API