diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-01-03 22:59:23 -0800 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-01-03 23:32:26 -0800 |
| commit | ba861a22198255bb461596e7fe6ec88248d1a2fe (patch) | |
| tree | 2ac661aa1ab5be9192967a8be910b0fe64ef1925 /db/migrate | |
| parent | fb4b0e6ca160ebc866deb95ae9e830993578ebe1 (diff) | |
| download | gitlab-ce-ba861a22198255bb461596e7fe6ec88248d1a2fe.tar.gz | |
Only validate project visibility when it has changedsh-skip-validation-visibility-changed
On GitLab.com, there are hundreds of projects that have visibility
levels that are inconsistent with the fork or group settings. Most
likely, this happened during a GitLab project import because the
validation was bypassed. Attempting to migrate these projects to hashed
storage fails even though the migration doesn't touch the visibility
settings. Skipping the visibility validation allows the migration to go
through.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55881
Diffstat (limited to 'db/migrate')
0 files changed, 0 insertions, 0 deletions