MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 171 Pull Requests 1 Releases 96 Wiki Activity

Product tier admin — define tiers and repo-to-tier mappings #627

New Issue
Open
opened 2026-06-12 08:00:27 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-12 08:00:27 +00:00
Owner
Copy Link
Copy Source

Phase 3.3 — Tier Management UI

Parent: #616 | Depends on: #624

Gitea template: templates/admin/license_tiers.tmpl

Admin page for defining product tiers:

  • Tier list showing: key, name, included repos, max domains, license count using this tier
  • Create/edit tier: name, key, select repos from org, set default max domains
  • Visual repo picker (checkboxes with repo icons)
  • Tier usage stats (how many licenses use each tier)
  • Warning before modifying a tier with active licenses (will rebuild all entitlements)

Acceptance criteria

  • CRUD for product tiers
  • Repo picker showing available org repos
  • Tier modification triggers entitlement rebuild for all affected licenses
  • Cannot delete a tier with active licenses (must reassign first)
## Phase 3.3 — Tier Management UI Parent: #616 | Depends on: #624 ### Gitea template: `templates/admin/license_tiers.tmpl` Admin page for defining product tiers: - Tier list showing: key, name, included repos, max domains, license count using this tier - Create/edit tier: name, key, select repos from org, set default max domains - Visual repo picker (checkboxes with repo icons) - Tier usage stats (how many licenses use each tier) - Warning before modifying a tier with active licenses (will rebuild all entitlements) ### Acceptance criteria - [ ] CRUD for product tiers - [ ] Repo picker showing available org repos - [ ] Tier modification triggers entitlement rebuild for all affected licenses - [ ] Cannot delete a tier with active licenses (must reassign first)
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Status —
Priority —
Type —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#627
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?