concretecms / core_splitter Goto Github PK

splitsh/lite replaces subtree split and enables the same sort of splitting we're doing and might solve for the odd hangs we get.

Let's assume that:

• in day 1 the main repo contains the branches A and B:
  the splitcore script correctly pushes those 2 branches to the final repo.
• in day 2 the main repo contains the branches A, and C:
  the splitcore script correctly pushes those 2 branches to the final repo, but it doesn't delete the remote branch B which doesn't exist anymore in the main repo.

For instance, we currently have the release/8.4.0 branch in the splitted repo but not in the main repo.

This can be solved in 2 ways:

1. we never delete branches in the main repo. But @aembler prefers to work directly on the main repo...
2. the splitcore deletes the refs that exists in the splitted repo but not in the original repo