The concurrency in replay part doesn't change anything unless you use the (brand new) instruction check-bunch. It's mostly there for testing and "I'm too lazy to rebase" reasons. Those are useful anyway if Camelus crashed for a while and you want to check a range of pr.
Now the last commit is more substantial, it fetches the pr from ocaml/opam-repository instead of the requester's repository. That way, the requester having a private repository (or deleting their branch) will not make Camelus sad.
The concurrency in replay part doesn't change anything unless you use the (brand new) instruction
check-bunch. It's mostly there for testing and "I'm too lazy to rebase" reasons. Those are useful anyway if Camelus crashed for a while and you want to check a range of pr.Now the last commit is more substantial, it fetches the pr from ocaml/opam-repository instead of the requester's repository. That way, the requester having a private repository (or deleting their branch) will not make Camelus sad.