Hugo Nijhuis
dd9c1c0090
Split gitea skill into main file and reference documentation. Main SKILL.md now focuses on core commands (154 lines, down from 201), with setup/auth and CI/Actions moved to reference files. Co-Authored-By: Claude Code <noreply@anthropic.com>
46 lines
938 B
Markdown
46 lines
938 B
Markdown
# Gitea Actions / CI
|
|
|
|
Commands for debugging CI/Actions workflow failures in Gitea.
|
|
|
|
## Workflow Runs
|
|
|
|
```bash
|
|
# List workflow runs
|
|
tea actions runs # List all workflow runs
|
|
tea actions runs -o json # JSON output for parsing
|
|
```
|
|
|
|
## Jobs
|
|
|
|
```bash
|
|
# List jobs for a run
|
|
tea actions jobs <run-id> # Show jobs for a specific run
|
|
tea actions jobs <run-id> -o json # JSON output
|
|
```
|
|
|
|
## Logs
|
|
|
|
```bash
|
|
# Get job logs
|
|
tea actions logs <job-id> # Display logs for a job
|
|
```
|
|
|
|
## Full Workflow: Find Failed Job Logs
|
|
|
|
```bash
|
|
# 1. Find the run ID
|
|
tea actions runs
|
|
|
|
# 2. Find the job ID from that run
|
|
tea actions jobs <run-id>
|
|
|
|
# 3. View the logs
|
|
tea actions logs <job-id>
|
|
```
|
|
|
|
## Tips
|
|
|
|
- Use `-o json` with runs/jobs for programmatic parsing
|
|
- Run IDs and Job IDs are shown in the output of the respective commands
|
|
- Logs are displayed directly to stdout (can pipe to `grep` or save to file)
|