Deleting wild repositories

With the example in the previous section, the administrator's job is much lightened (albeit at the expense of some loss of control). However, there still remains one feature that your users will eventually want: deleting repositories that have served their purpose.

In order to allow users to delete repositories that they have created (it need not be said that a user cannot delete anything else!), the administrator needs to enable the D command by uncommenting the corresponding line in the list of commands in $HOME/.gitolite.rc. Then the user can run the D command to delete repositories.

Repositories are locked against accidental deletion by default, so every delete is actually two steps—the unlock sub-command, then the ...

Get Gitolite Essentials now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.