MokoConsulting/MokoCLI
Public Access
1
0
Fork 0
Code Issues 3 Pull Requests Releases 8 Wiki Activity

feat: support .mokogitea/workflows/custom/ subfolder discovery in workflow_sync #314

New Issue
Open
opened 2026-06-23 18:05:46 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-23 18:05:46 +00:00
Owner
Copy Link
Copy Source

Summary

When MokoGitea-Fork adds subfolder workflow discovery (see MokoGitea-Fork issue), update workflow_sync.php to also preserve workflows in .mokogitea/workflows/custom/ during sync — in addition to the custom- prefix convention.

Current State

workflow_sync.php currently uses custom- prefix convention to protect repo-specific workflows from deletion during sync. Once Gitea supports subfolder discovery, the cleaner approach is a custom/ subfolder.

Depends On

MokoGitea-Fork: subfolder workflow discovery feature.

## Summary When MokoGitea-Fork adds subfolder workflow discovery (see MokoGitea-Fork issue), update `workflow_sync.php` to also preserve workflows in `.mokogitea/workflows/custom/` during sync — in addition to the `custom-` prefix convention. ## Current State `workflow_sync.php` currently uses `custom-` prefix convention to protect repo-specific workflows from deletion during sync. Once Gitea supports subfolder discovery, the cleaner approach is a `custom/` subfolder. ## Depends On MokoGitea-Fork: subfolder workflow discovery feature.
Sign in to join this conversation.
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoCLI#314
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?