delete a folder from client machine, if git previleges are revoked

We have around 100 devs working on different project, usually in teams of 2-3 devs, and a project lasts for around 1 week max, we have a local gitlab setup, through which version control is taken care off.
We also revoke the privileges on a project once its over, so they couldn’t make any amends without the knowledge of a senior; Is it possible to make sure that the local git mapped folder gets deleted if the privileges are revoked and the user tries to do a git pull.
The developers have a mix of windows, linux and mac machines, so I don’t think its possible to have a daemon script which deletes the folders for which privileges are revoked.
One more idea I have is to keep the entire data on the NAS and delete the directories at NAS if the git privileges are revoked or the manager identifies and closes a project for further development.

  • Rename a file on git and keep history
  • Download Github .zip without Repository's name folder
  • How to add multiple projects into a Single repository in Bitbucket?
  • How do i add a command line prompt as the $EDITOR when committing in svn and git
  • Git fast forward is (strictly pointerwise) actually fast reverse? Terminology disambiguation for Git newbies
  • Git - accept push only from a named repository
  • Removing file pattern with git-update-index --remove
  • Understanding GIT workflow a little better
  • How to store my password and login for my remote repository?
  • How does Git determine what objects need to be sent between repositories?
  • development branch with multiple parallel releases
  • fatal: bad config file line in .gitconfig file when making an alias for deleting merged branches
  • One Solution collect form web for “delete a folder from client machine, if git previleges are revoked”

    Is it possible to make sure that the local git mapped folder gets deleted if the privileges are revoked and the user tries to do a git pull.

    If the privileges are revoked on the central GitLab instance, the developer won’t be able to to a git pull (or git push).

    But you cannot control/enforce what is happening locally. Only centrally on the GitLab side.

    In a decentralized environment (which is what git allows you to manage, as a Distributed VCS), you can control how the downstream repos interact with you (through Access Control Level, with gitolite or gitlab-shell), but you cannot access directly the downstream environments themselves.

    Git Baby is a git and github fan, let's start git clone.