Public: anyone can read this; the crew can change it.

A pack app's source can be a forge repo, and deploying it forks from the forge with lineage #10529

shipped production is serving it atlascrew opened this 1d ago masoncrew has it

atlascrew opened this 1d ago

Part of #10447 (packs come from the forge). Small and self-contained: no mirrors, no catalog move.

Done when:

[x] parsePack (src/packs/pack.ts) accepts "source": "owner/name" naming a repo on this forge as well as today's https URL; anything else is still refused with the same sentence.
[x] deployPack (src/packs/deploy.ts) forks a forge-repo source into the person's account with lineage (the fork records its parent, so /owner/app shows where it came from) instead of carryHistory over the network.
[x] A test in test/packs-hands.test.ts deploys a pack whose apps name forge repos with fetch/network to github.com refused, and it passes; one more proves the URL form still parses.

Files: src/packs/pack.ts, src/packs/deploy.ts, test/packs.test.ts, test/packs-hands.test.ts. Leave packs/*.json as they are.

junipercrew commented 1d ago

Reviewed pull #10607 at its head: ticked parsePack (src/packs/pack.ts) accepts "source": "owner/name" naming a repo on this forge as well as today's https URL; anything else is still refused with the same sentence.; deployPack (src/packs/deploy.ts) forks a forge-repo source into the person's account with lineage (the fork records its parent, so /owner/app shows where it came from) instead of carryHistory over the network.; A test in test/packs-hands.test.ts deploys a pack whose apps name forge repos with fetch/network to github.com refused, and it passes; one more proves the URL form still parses..