MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 142 Pull Requests Releases 89 Wiki Activity

feat(updates): org-level default update streams with per-repo override #265

New Issue
Open
opened 2026-05-31 01:45:14 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-31 01:45:14 +00:00
Owner
Copy Link
Copy Source

Summary

Add org-level default update stream configuration that repos inherit, with per-repo override capability.

Org-level defaults

  • Org settings page to configure default update streams
  • Option to use standard Joomla streams (stable, release-candidate, beta, alpha, development) or define custom tags
  • Custom tags example: lts, nightly, security, canary
  • All repos in the org inherit these defaults

Per-repo override

  • Repo settings can override the org default
  • Toggle: "Use org defaults" or "Custom streams"
  • When custom, repo defines its own stream tags and tag-matching rules

Data model

  • org_update_config table or extend org settings
  • Fields: org_id, stream_mode (joomla/custom), custom_streams (JSON array), tag_patterns (JSON map of stream->regex)

Tag matching

Default Joomla patterns:

  • stable: tags without prerelease suffix
  • release-candidate: -rc suffix
  • beta: -beta suffix
  • alpha: -alpha suffix
  • development: -dev suffix

Custom example:

  • lts: -lts suffix (long-term support)
  • security: -security suffix
  • nightly: -nightly suffix

Created by @MokoBot - Claude Opus 4.6

## Summary Add org-level default update stream configuration that repos inherit, with per-repo override capability. ### Org-level defaults - Org settings page to configure default update streams - Option to use standard Joomla streams (stable, release-candidate, beta, alpha, development) or define custom tags - Custom tags example: lts, nightly, security, canary - All repos in the org inherit these defaults ### Per-repo override - Repo settings can override the org default - Toggle: "Use org defaults" or "Custom streams" - When custom, repo defines its own stream tags and tag-matching rules ### Data model - org_update_config table or extend org settings - Fields: org_id, stream_mode (joomla/custom), custom_streams (JSON array), tag_patterns (JSON map of stream->regex) ### Tag matching Default Joomla patterns: - stable: tags without prerelease suffix - release-candidate: -rc suffix - beta: -beta suffix - alpha: -alpha suffix - development: -dev suffix Custom example: - lts: -lts suffix (long-term support) - security: -security suffix - nightly: -nightly suffix --- *Created by @MokoBot - Claude Opus 4.6*
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
 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
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#265
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?