Name |
Last commit
|
Last update |
---|---|---|
.. | ||
backup.rake | ||
enable_automerge.rake | ||
gitolite_rebuild.rake | ||
setup.rake | ||
status.rake | ||
test.rake | ||
update_hooks.rake |
BigW Consortium Gitlab
Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and restore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
backup.rake | Loading commit data... | |
enable_automerge.rake | Loading commit data... | |
gitolite_rebuild.rake | Loading commit data... | |
setup.rake | Loading commit data... | |
status.rake | Loading commit data... | |
test.rake | Loading commit data... | |
update_hooks.rake | Loading commit data... |