(refs #1608)Fix updating parent repository relationship bug when repository is renamed or transferred.
1 parent 5a8516e commit b0057481d81c7ad3c3733825d6971b5b98d5b442
@Naoki Takezoe Naoki Takezoe authored on 24 May 2017
Showing 1 changed file
View
2
■■■
src/main/scala/gitbucket/core/service/RepositoryService.scala
}.map { t => t.originUserName -> t.originRepositoryName }.update(newUserName, newRepositoryName)
 
Repositories.filter { t =>
(t.parentUserName === oldUserName.bind) && (t.parentRepositoryName === oldRepositoryName.bind)
}.map { t => t.originUserName -> t.originRepositoryName }.update(newUserName, newRepositoryName)
}.map { t => t.parentUserName -> t.parentRepositoryName }.update(newUserName, newRepositoryName)
 
// Updates activity fk before deleting repository because activity is sorted by activityId
// and it can't be changed by deleting-and-inserting record.
Activities.filter(_.byRepository(oldUserName, oldRepositoryName)).list.foreach { activity =>