MokoConsulting/mokoplatform
1
0
Fork 0
Code Issues 9 Pull Requests Releases 8 Wiki Activity

chore: feature branch versions should stay in sync with dev #250

New Issue
Open
opened 2026-06-06 19:22:03 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-06 19:22:03 +00:00
Owner
Copy Link
Copy Source

When dev gets a version bump (e.g. via pre-release workflow), feature branches diverge and show stale versions. Feature branches should either:\n\n1. Auto-rebase/merge from dev when version bumps happen\n2. Or the version bump should propagate to open feature branches\n\nCurrently feature branches are created from dev but never updated when dev's version increments. This causes confusion when reviewing PRs (version mismatch).

When dev gets a version bump (e.g. via pre-release workflow), feature branches diverge and show stale versions. Feature branches should either:\n\n1. Auto-rebase/merge from dev when version bumps happen\n2. Or the version bump should propagate to open feature branches\n\nCurrently feature branches are created from dev but never updated when dev's version increments. This causes confusion when reviewing PRs (version mismatch).
jmiller commented 2026-06-06 19:22:05 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/250-chore-feature-branch-versions-should-sta

git fetch origin
git checkout feature/250-chore-feature-branch-versions-should-sta
Branch created: [`feature/250-chore-feature-branch-versions-should-sta`](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/src/branch/feature/250-chore-feature-branch-versions-should-sta) ```bash git fetch origin git checkout feature/250-chore-feature-branch-versions-should-sta ```
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 -
Type Task
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/mokoplatform#250
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?