Files
tendril/kb/02_systems/2025-11-11--gitea-actions-guide--howto.md
Gitea Actions 5b8bf62130
All checks were successful
KB Lint / validate (push) Successful in 24s
docs(kb): migrate Gitea documentation to KB system
Migrated all Gitea documentation from docs/GITEA/ folder into the Knowledge
Base system, following KB naming conventions and frontmatter requirements.

## What Was Migrated

### Gitea Documentation Guides (6 KB entries)

1. **Gitea Basics Guide** ()
   - Core concepts and features of Gitea
   - Key differences from GitHub
   - Terminology and common workflows
   - System requirements

2. **Gitea Actions Guide** ()
   - Gitea Actions CI/CD system
   - Compatibility with GitHub Actions
   - Workflow creation and patterns
   - Troubleshooting guide

3. **LLM Guidelines for Gitea** ()
   - Terminology guidelines for LLMs
   - Documentation standards
   - Common scenarios and checklist
   - Quick reference

4. **Gitea Workflows Guide** ()
   - Common workflows (repository setup, branches, PRs, issues)
   - Best practices (branch naming, commits, PR process)
   - Integration with documentation systems
   - Troubleshooting

5. **Gitea API Reference** ()
   - API authentication and endpoints
   - Differences from GitHub API
   - Common use cases
   - MCP server integration

6. **Gitea Documentation Overview** ()
   - Overview and index of all Gitea documentation
   - Quick reference guide
   - Links to all Gitea KB entries

## KB System Compliance

 All files follow KB naming convention (YYYY-MM-DD--slug--type.md)
 All files have complete frontmatter (all 18 required fields)
 All files categorized in 02_systems/ (infrastructure/tooling)
 All files reference original documentation location
 KB changelog updated with migration entry
 KB index regenerated via script (8 files, 23 topics, 31 tags)

## Category Decision

All Gitea documentation entries were placed in **02_systems/** category
because:
- Gitea is infrastructure/tooling (not project-specific)
- Documentation covers platform usage and integration
- Guides are system-level references
- Fits KB category definition: "Infrastructure, DevOps, tooling"

## Original Documentation

Original documentation remains in  folder:
- docs/GITEA/Gitea-Basics.md
- docs/GITEA/Gitea-Actions-Guide.md
- docs/GITEA/LLM-Gitea-Guidelines.md
- docs/GITEA/Gitea-Workflows.md
- docs/GITEA/Gitea-API-Reference.md
- docs/GITEA/README.md

KB entries reference original locations for full documentation.

## Benefits

- Gitea documentation now searchable via KB index
- Integrated with KB system for LLM discovery
- Consistent with other KB entries
- Maintains reference to original documentation
- Provides comprehensive Gitea platform reference
2025-11-11 12:36:12 -07:00

4.7 KiB

title, date, captured_at, author, source, source_type, project, related_projects, topics, tags, type, status, phase_relevance, routing_hint, proposed_path, routing_confidence, related, summary, key_takeaways, action_candidates
title date captured_at author source source_type project related_projects topics tags type status phase_relevance routing_hint proposed_path routing_confidence related summary key_takeaways action_candidates
Gitea Actions Guide 2025-11-11 2025-11-11
datawarrior
kind ref
doc docs/GITEA/Gitea-Actions-Guide.md
personal_note
tendril
tendril
gitea
actions
ci-cd
workflows
automation
gitea
actions
ci-cd
workflows
automation
github-compatible
howto active
phase-03
Gitea Actions CI/CD guide - infrastructure/tooling documentation kb/02_systems/ 0.95
docs/GITEA/Gitea-Actions-Guide.md
.github/workflows/
Comprehensive guide to Gitea Actions (CI/CD system compatible with GitHub Actions). Covers compatibility, workflow creation, common patterns, troubleshooting, and LLM documentation guidelines.

Gitea Actions Guide

Overview

Gitea Actions is Gitea's CI/CD system that is compatible with GitHub Actions. This means:

  • Same YAML workflow format
  • Same .github/workflows/ directory structure
  • Same triggers and syntax
  • Existing GitHub Actions workflows work with minimal or no modifications
  • Actions plugins can be downloaded from any Git website

Key Compatibility Points

1. Directory Structure

Same as GitHub:

.github/
└── workflows/
    ├── workflow1.yml
    ├── workflow2.yml
    └── ...

2. YAML Format

Identical to GitHub Actions - Same workflow syntax, triggers, jobs, steps

3. Triggers

Same triggers as GitHub Actions:

  • push - On push to repository
  • pull_request - On pull request events
  • workflow_dispatch - Manual trigger
  • schedule - Scheduled runs (cron syntax)
  • repository_dispatch - External events

4. Runners

  • Gitea Runners (similar to GitHub Runners)
  • Self-hosted runners
  • Can run on various platforms
  • Register runners with Gitea instance

Differences from GitHub Actions

  1. Actions Marketplace

    • GitHub: Centralized marketplace
    • Gitea: Actions can be downloaded from any Git website
  2. Runner Registration

    • GitHub: Runners managed by GitHub (or self-hosted)
    • Gitea: All runners are self-hosted
  3. Some GitHub-Specific Features

    • Some GitHub Actions features may not be available
    • Check Gitea Actions documentation for specific limitations
    • Most common workflows work identically

Common Workflow Patterns

Linting Workflow

name: Lint

on:
  push:
    paths:
      - 'src/**/*.rs'
  pull_request:
    paths:
      - 'src/**/*.rs'

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run linter
        run: cargo clippy

Testing Workflow

name: Test

on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run tests
        run: cargo test

Index Update Workflow

name: Update Index

on:
  push:
    branches: [ main ]
    paths:
      - 'kb/**/*.md'

jobs:
  update:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Generate index
        run: ./kb/scripts/generate-index.sh
      - name: Commit changes
        run: |
          git config user.name "Gitea Actions"
          git config user.email "actions@gitea.io"
          git add kb/_index.md
          git commit -m "chore: update KB index" || exit 0
          git push

For LLMs: Documentation Guidelines

When Creating Workflow Documentation

  1. Reference as "Gitea Actions":

    • "This workflow runs in Gitea Actions"
    • "Gitea Actions will execute this workflow on push"
  2. Note Compatibility:

    • "Gitea Actions is compatible with GitHub Actions"
    • "This workflow uses the same YAML format as GitHub Actions"
  3. Use Correct Terminology:

    • "Gitea Actions workflows" (not "GitHub Actions workflows")
    • "Gitea Runners" (not "GitHub Runners")
    • But note: "Same format as GitHub Actions"

Troubleshooting

Workflow Not Running

  1. Check runner registration
  2. Check workflow syntax
  3. Check triggers
  4. Check permissions

Actions Not Found

  1. Check action source
  2. Check network access
  3. Use full URL for custom actions

Runner Issues

  1. Check runner status
  2. Check runner labels
  3. Check runner logs

References


Original Location: docs/GITEA/Gitea-Actions-Guide.md
Last Updated: 2025-01-27
Related:

  • .github/workflows/ - Workflow files
  • docs/GITEA/Gitea-Basics.md
  • docs/GITEA/Gitea-Workflows.md