MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 163 Pull Requests Actions Packages Licenses 2 Releases 68 Wiki Activity

feat(licenses): package repo scope UI — assign packages to specific repos #395

New Issue
Open
opened 2026-06-01 10:01:14 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-01 10:01:14 +00:00
Owner
Copy Link
Copy Source

Summary

The RepoScope field on LicensePackage exists (TEXT, default 'all') but is always set to 'all'. Need UI to let admins scope a package to:

  • All repos in the org
  • A single specific repo
  • Multiple selected repos

Requirements

  • Dropdown/multiselect in create and edit package forms
  • List org repos for selection
  • Store as JSON array of repo IDs, or 'all'
  • ValidateLicenseKey should check if the repo requesting validation is in scope

Test Plan

  • Create package scoped to single repo → key only works for that repo's update feed
  • Create package scoped to 'all' → key works for all repos
  • Create package scoped to 2 repos → key works for both but not others
  • Edit package scope → changes apply immediately

🤖 Generated with Claude Code

## Summary The `RepoScope` field on LicensePackage exists (TEXT, default 'all') but is always set to 'all'. Need UI to let admins scope a package to: - All repos in the org - A single specific repo - Multiple selected repos ## Requirements - Dropdown/multiselect in create and edit package forms - List org repos for selection - Store as JSON array of repo IDs, or 'all' - ValidateLicenseKey should check if the repo requesting validation is in scope ## Test Plan - [ ] Create package scoped to single repo → key only works for that repo's update feed - [ ] Create package scoped to 'all' → key works for all repos - [ ] Create package scoped to 2 repos → key works for both but not others - [ ] Edit package scope → changes apply immediately 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller commented 2026-06-01 10:12:51 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan — Package Repo Scope

API

  • Create package with repo_scope="all" → key validates for any repo in org
  • Create package with repo_scope=[repoID] → key only validates for that repo's update feed
  • Create package with repo_scope=[id1,id2] → key validates for both repos
  • Validate key on out-of-scope repo → rejected
  • Edit package scope → changes apply immediately

GUI

  • Repo scope selector in create package form (dropdown/multiselect)
  • Shows org repos for selection
  • "All repos" option (default)
  • Edit package form shows current scope selection
  • Scope displayed in packages table

🤖 Generated with Claude Code

## Testing Plan — Package Repo Scope ### API - [ ] Create package with repo_scope="all" → key validates for any repo in org - [ ] Create package with repo_scope=[repoID] → key only validates for that repo's update feed - [ ] Create package with repo_scope=[id1,id2] → key validates for both repos - [ ] Validate key on out-of-scope repo → rejected - [ ] Edit package scope → changes apply immediately ### GUI - [ ] Repo scope selector in create package form (dropdown/multiselect) - [ ] Shows org repos for selection - [ ] "All repos" option (default) - [ ] Edit package form shows current scope selection - [ ] Scope displayed in packages table 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller added the pending: testing label 2026-06-01 10:13:56 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
 pending: testing
Feature implemented but not yet tested with documented proof
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 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
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 type: bug
Something isn't working
 type: bug
type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels pending: testing
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#395
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?