There seems to be no way to specify a branch to clone, or a sub directory to use.
Branch cloning is critical for replicating PR’s. That would give any reviewer a clean, exact, up-to-date, editable, safe copy of the PR in question… which can’t be done with Replit at the moment.
The branch isn’t a git repository, so you can’t clone it. Maybe download a .tar.gz for the repo, move the part you want out of the downloaded files, delete the original part, and then move the part you wanted into the base directory for the repl.
Indeed… the issue with that is that I’ll have my own container, with it’s own stateful configuration and side effects. A PR link should be an exact stateless reproduction of the modifications made, without having to ask the maintainers to figure it out themselves. Not only that, they can’t really try properly without privileged access I would have to give them… if git is used, that’s not secure to do with strangers.
That gives any reviewer a clean, exact, up-to-date, editable, safe copy of the PR in question… which can’t be done with Replit at the moment.
Git repo:
StackBlitz Classic uses a worker to pull the contents from git, similar to Replit.
Their new VS Code based version, CloudFlow, clones from git exclusively, and has a browser based git with a CORS proxy… it’s trippy, but inherently hamstrung by browser security GitHub - FossPrime/fsh: Created with StackBlitz ⚡️
If manually run by the PR reviewer that does work… but there’s no way to pass that command to post-onBoot or onBoot. Speaking of which StackBlitz also has a way to pass commands to npm run from a link. It’s secured by not allowing for arguments, slow performance and the inherent whitelist of allowed commands in package.json.