Monorepo design

[caendesilva]

(OUTDATED)

From the original Monorepo readme:

Experimenting with a monorepo. The way I'm thinking is that this repo (when/if transferred to the Hyde org)
is the master origin and source of truth for all HydePHP packages. When a release is tagged here, a CI action
propagates the tag and changes to all* HydePHP packages and creates subsequent releases.

Some packages, like hyde/hyde will need some processing after the merge. For example, the composer.json
should be reverted to not use the dev-master branch.

*Some packages, like HydeFront may not need to have their tags synced. Thinking it is mainly for
hyde/hyde and hyde/framework as they are tightly coupled.

[caendesilva]

Monorepo CI/CD Operations

Splitting Overview (OUTDATED)

flowchart LR

  op[on push] 
  
  op --> phd
  op --> pfr
  op --> prc
    
  subgraph sm[split-monorepo.yml]
        subgraph hhd[handle hyde]
             phd[apply transformations] -.- shd[split into mirror branch] --> dhd[push mirror to readonly repositories]
        end 
        subgraph hfr[handle framework]
            pfr[package source directory to artifact] --> sfr[split into mirror branch] --> dfr[push mirror to readonly repositories]
        end
        subgraph hrc[handle realtime-compiler]
            prc[package source directory to artifact] --> src[split into mirror branch] --> drc[push mirror to readonly repositories]
        end
    end

Loading