For example,
if Georg clones a project with a post-clone hook,
then Timmy updates said project's post-clone hook, configuring it to install additional dependencies (without which the new version of this project will not work),
and then Georg clones the new version of the project
It is the case that Georg needs the post-clone hook to run again. It is a burden (and a faulty procedure) to have to run the post-clone hook manually. Find a way to provide automatic re-runs of the post-clone hook upon "magic token" checkouts.
For example,
if Georg clones a project with a post-clone hook,
then Timmy updates said project's post-clone hook, configuring it to install additional dependencies (without which the new version of this project will not work),
and then Georg clones the new version of the project
It is the case that Georg needs the post-clone hook to run again. It is a burden (and a faulty procedure) to have to run the post-clone hook manually. Find a way to provide automatic re-runs of the post-clone hook upon "magic token" checkouts.