openvibers/openvibe.link Commits

Clone to this computer, from the page's button (#149)

OP OpenVibers committed 3 days ago · tag v0.53. · 0 files, +0 −0

* Clone to this computer, from the page's button

The watch that `openvibe-link git connect` already holds now carries a clone request as well as the read-only
tree, file and log questions: the repository page picks this computer, Git sends the repository, the https clone
URL with a short read token, who asked and when the two minutes end. Link asks the person here — the repository,
who asked, the folder and the time left, then y/N, or --yes for a script — and writes nothing before that answer.

The checks are the ones `openvibe-link clone` already made, now shared by both paths: the root the person chose,
nothing outside it after symlinks, a non-empty folder only after a second answer, one clone at a time, an expired
request refused. Each step goes back over the machine's own link: waiting, approved, cloning with git's percentage,
done with the folder, refused or failed with git's last line.

Version 0.53.0.

Checked: go test -race ./internal/gitrelay ./cmd/openvibe-link — each refusal leaves the disk untouched, an approved
clone lands under the root, and the approval reads y/N.

* Compare the clone's folder by name, as macOS and Windows report it

The root may be a symlink (macOS /var) or reached through a short name (Windows RUNNER~1), so the machine's
reported folder is not the test's root + "demo". Read through the reported path instead.