Hi @pubuzhixing8,
We reviewed the current remote branch inventory because the repository has accumulated many long-lived topic, test, migration, and release branches. There are currently 46 remote branches, which makes active work harder to identify and leaves the repository difficult to scan.
Findings
- The default branch is
develop.
- Only
develop and master are marked as protected.
- Only three branches currently have open pull requests:
- 40 branches have had no commits for more than six months.
- CI explicitly targets
develop; we found no repository workflow that requires the historical topic branches.
delete_branch_on_merge is already enabled, so this appears to be mostly historical backlog plus branches from closed or non-PR work.
Proposed short-term state
Reduce the repository from 46 branches to 6 initially:
- Keep
develop.
- Keep the three open-PR branches until their PRs finish.
- Temporarily retain
master while confirming whether it still has a stable-release responsibility.
- Temporarily retain
mcp_plait while deciding whether its unmerged work should be merged, moved to a separate repository, or archived.
After the open PRs finish, their branches should be removed automatically.
High-confidence cleanup candidates
These appear safe or strongly justified for cleanup because their PR was merged/closed, their tip is already contained in develop, or an exact release tag preserves the tip:
Candidates that should be archived or confirmed with the owner before deletion
These have commits not directly reachable from develop, but have no open PR and no recent maintenance evidence:
0.62.0-next.5angular-v19elment-flavourexport-filefish-boneinit-table-creationisland-hostmeasure-texttable-edittext-measuretext-safariv0.60.0-ltsv0.61.xw/#WIK-15429wumeimin/ai-toolswumeimin/arrow-line-connectionwumeimin/mcp_draftwumeimin/toolswumeimin/tools-and-prompt-1020xl/update18xws/#demoMoveToCenterxws/#fixz-index-all
For these branches, we suggest either obtaining explicit owner confirmation or preserving the exact tip with an annotated archive tag before deleting the branch.
Requested review
@pubuzhixing8, could you please review this inventory and help decide/handle the cleanup?
In particular:
The goal is not to delete work blindly, but to make active development visible and keep the remote branch list intentional and maintainable.
Hi @pubuzhixing8,
We reviewed the current remote branch inventory because the repository has accumulated many long-lived topic, test, migration, and release branches. There are currently 46 remote branches, which makes active work harder to identify and leaves the repository difficult to scan.
Findings
develop.developandmasterare marked as protected.codex/normalize-table-cells-order— fix(draw): normalize swimlane cell order #1157codex/table-resize-cell-edges— fix(draw): adjust table cell edge resize #1151nightt5879/fix-temporary-hand-gesture— fix(core): isolate Space panning from active tools #1153develop; we found no repository workflow that requires the historical topic branches.delete_branch_on_mergeis already enabled, so this appears to be mostly historical backlog plus branches from closed or non-PR work.Proposed short-term state
Reduce the repository from 46 branches to 6 initially:
develop.masterwhile confirming whether it still has a stable-release responsibility.mcp_plaitwhile deciding whether its unmerged work should be merged, moved to a separate repository, or archived.After the open PRs finish, their branches should be removed automatically.
High-confidence cleanup candidates
These appear safe or strongly justified for cleanup because their PR was merged/closed, their tip is already contained in
develop, or an exact release tag preserves the tip:#WIK-14735— PR feat(draw): support rotate resize #WIK-14735 #773 merged#WIK-15207— PR fix(list-render): fix g hierarchy when add group and move element #WIK-15207 #841 mergedadjust-table-resize— PR feat(core): adjust table resize #931 closed; appears superseded by the current fix(draw): adjust table cell edge resize #1151 workcodex/pr-1137-conflict— temporary conflict branch for merged PR feat(draw): add fillStyle support for shapes #1137publish-test— old release-test branch; tip is preserved by@plait/*@0.46.0tagsrename-line— PR refactor: rename #978 mergedtable— fully contained indevelopv0.53.1— exactv0.53.1tag existsv18.x— fully contained indevelopw/#WIK-14309— PR refactor(core): uniformly handle clipboard data and add parameter for setFragment and insertFragment #WIK-14309 #701 mergedw/#WIK-14310— fully contained indevelopw/#WIK-14486— PR feat(draw): draw equal line when aspect ratio resize #WIK-14486 #747 mergedw/#WIK-14841— PR feat(mind): support mindmap group and add canAddToGroup #WIK-14841 #781 mergedw/#WIK-14934— fully contained indevelopw/#WIK-15348— PR feat(draw): support bind element to table #875 closedw/test— old test branch with no PRzw/#TINFR-2712— PR build: bump ng v20 #TINFR-2712 #1129 merged intodevelopCandidates that should be archived or confirmed with the owner before deletion
These have commits not directly reachable from
develop, but have no open PR and no recent maintenance evidence:0.62.0-next.5angular-v19elment-flavourexport-filefish-boneinit-table-creationisland-hostmeasure-texttable-edittext-measuretext-safariv0.60.0-ltsv0.61.xw/#WIK-15429wumeimin/ai-toolswumeimin/arrow-line-connectionwumeimin/mcp_draftwumeimin/toolswumeimin/tools-and-prompt-1020xl/update18xws/#demoMoveToCenterxws/#fixz-index-allFor these branches, we suggest either obtaining explicit owner confirmation or preserving the exact tip with an annotated archive tag before deleting the branch.
Requested review
@pubuzhixing8, could you please review this inventory and help decide/handle the cleanup?
In particular:
masterstill serves an active release purpose.mcp_plaitshould be merged, extracted, or archived.developplus any release branch with an explicit maintenance responsibility.The goal is not to delete work blindly, but to make active development visible and keep the remote branch list intentional and maintainable.