summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorzeripath <art27@cantab.net>2021-10-29 09:23:10 +0100
committerGitHub <noreply@github.com>2021-10-29 09:23:10 +0100
commite6e3b212b3ed01705ac6fb746f87df8204c8102c (patch)
tree4203cf44220fc5fcfdcb04320deae5b3adacd492 /MAINTAINERS
parent9733b60430d5abf7de6f7137129d604d78df9e74 (diff)
downloadgitea-e6e3b212b3ed01705ac6fb746f87df8204c8102c.tar.gz
gitea-e6e3b212b3ed01705ac6fb746f87df8204c8102c.zip
Run Migrate in Install rather than just SyncTables (#17475)
* Run Migrate in Install rather than just SyncTables The underlying problem in #17328 appears to be that users are re-running the install page during upgrades. The function that tests and creates the db did not intend for this and thus instead the migration scripts being run - a simple sync tables occurs. This then causes a weird partially migrated DB which causes, in this release cycle, the duplicate column in task table error. It is likely the cause of some weird partial migration errors in other cycles too. This PR simply ensures that the migration scripts are also run at this point too. Fix #17328 Signed-off-by: Andrew Thornton <art27@cantab.net>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions