Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Research and configure Gitea provider: workflows, skills, labels, and content rules #1

New Issue
Closed
opened 2026-06-20 16:16:21 +00:00 by Claude · 0 comments
Claude commented 2026-06-20 16:16:21 +00:00
Collaborator
Copy Link

0029 — Gitea provider: research and configure workflows, skills, and content

Type: HOTL
Parent PRD: standalone

Context

Skills and agents that touch the issue tracker (/to-issues, /to-prd, /triage) currently have no Gitea-specific guidance — they would guess at labels, milestones, and conventions. This issue covers the research and configuration needed to make Gitea the reliable active backend.

Tasks

  1. Audit current Gitea setup — what repos exist, what labels/milestones are configured, what MCP tools are available, what's already wired
  2. Define providers/gitea/instructions.md — default repo target, label taxonomy, milestone conventions (how chunks map to milestones), branch naming, PR template, issue structure rules
  3. Audit existing skills that touch the issue tracker (/to-issues, /to-prd, /triage) — identify where Gitea-specific behavior needs to be branched or documented
  4. Determine whether a Gitea-specific skill or agent is warranted, or whether providers/gitea/instructions.md is sufficient
  5. Configure Gitea labels and milestones to match the conventions defined in step 2

Acceptance criteria

  • providers/gitea/instructions.md exists and covers: default repo, label taxonomy, milestone structure, branch naming, PR template, issue format expectations
  • Running /to-issues with Gitea MCP active produces issues consistent with the conventions — no ad-hoc label guessing
  • Any decision to add or skip a Gitea-specific skill is documented (inline note in instructions.md is sufficient; ADR only if the decision is hard to reverse)
  • Gitea labels and milestones match the defined taxonomy
# 0029 — Gitea provider: research and configure workflows, skills, and content **Type:** HOTL **Parent PRD:** standalone ## Context Skills and agents that touch the issue tracker (`/to-issues`, `/to-prd`, `/triage`) currently have no Gitea-specific guidance — they would guess at labels, milestones, and conventions. This issue covers the research and configuration needed to make Gitea the reliable active backend. ## Tasks 1. Audit current Gitea setup — what repos exist, what labels/milestones are configured, what MCP tools are available, what's already wired 2. Define `providers/gitea/instructions.md` — default repo target, label taxonomy, milestone conventions (how chunks map to milestones), branch naming, PR template, issue structure rules 3. Audit existing skills that touch the issue tracker (`/to-issues`, `/to-prd`, `/triage`) — identify where Gitea-specific behavior needs to be branched or documented 4. Determine whether a Gitea-specific skill or agent is warranted, or whether `providers/gitea/instructions.md` is sufficient 5. Configure Gitea labels and milestones to match the conventions defined in step 2 ## Acceptance criteria - [x] `providers/gitea/instructions.md` exists and covers: default repo, label taxonomy, milestone structure, branch naming, PR template, issue format expectations - [x] Running `/to-issues` with Gitea MCP active produces issues consistent with the conventions — no ad-hoc label guessing - [x] Any decision to add or skip a Gitea-specific skill is documented (inline note in `instructions.md` is sufficient; ADR only if the decision is hard to reverse) - [x] Gitea labels and milestones match the defined taxonomy
Defame1297 added this to the The great refactoring milestone 2026-06-25 20:07:14 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone The great refactoring
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?