BigW Consortium Gitlab
Trigger hooks create on backup restore Number of users migrating from installation from source to omnibus get this issue. This can be fixed with a bash one liner but we already have a script that creates hooks in gitlab-shell. Added to gitlab:shell:install task call to `bin/create-hooks`. This script is idempotent which means it will only rewrite hooks if something changed. Fixes https://dev.gitlab.org/gitlab/gitlabhq/issues/2208, https://github.com/gitlabhq/gitlabhq/issues/9101 and for the most part https://github.com/gitlabhq/gitlabhq/issues/8161 See merge request !762
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
db | Loading commit data... | |
backup.rake | Loading commit data... | |
bulk_add_permission.rake | Loading commit data... | |
check.rake | Loading commit data... | |
cleanup.rake | Loading commit data... | |
enable_automerge.rake | Loading commit data... | |
generate_docs.rake | Loading commit data... | |
import.rake | Loading commit data... | |
info.rake | Loading commit data... | |
mail_google_schema_whitelisting.rake | Loading commit data... | |
setup.rake | Loading commit data... | |
shell.rake | Loading commit data... | |
sidekiq.rake | Loading commit data... | |
task_helpers.rake | Loading commit data... | |
test.rake | Loading commit data... | |
web_hook.rake | Loading commit data... |