Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 6 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

refactor: split manage_labels.py into reusable modes #6

New Issue
Open
opened 2026-06-21 17:16:26 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-06-21 17:16:26 -05:00
Owner
Copy Link
Copy Source

The MAPPING dict in manage_labels.py is a one-time backfill of issue-to-label assignments. Split into:

  • --create-labels — idempotent label creation (reusable)
  • --apply-mapping — one-off issue labeling from the hardcoded dict
  • --add-label <issue> <label> — ad-hoc single-issue labeling

Low priority — the current script works fine for its purpose.

The MAPPING dict in `manage_labels.py` is a one-time backfill of issue-to-label assignments. Split into: - `--create-labels` — idempotent label creation (reusable) - `--apply-mapping` — one-off issue labeling from the hardcoded dict - `--add-label <issue> <label>` — ad-hoc single-issue labeling Low priority — the current script works fine for its purpose.
jcwalker3 added the nice-to-have label 2026-06-21 17:16:46 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
chore
documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 important
mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
read-only
Read-only, no mutation
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
No Label nice-to-have
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#6
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?