sillyguodong bfecf3bd89 Fix internal sever error when visiting a PR that bound to the deleted team (#24127) ... Close: #23738 The actual cause of `500 Internal Server Error` in the issue is not what is descirbed in the issue. The actual cause is that after deleting team, if there is a PR which has requested reivew from the deleted team, the comment could not match with the deleted team by `assgin_team_id`. So the value of `.AssigneeTeam` (see below code block) is `nil` which cause `500 error`. 1c8bc4081a/templates/repo/issue/view_content/comments.tmpl (L691-L695) To fix this bug, there are the following problems to be resolved: - [x] 1. ~~Stroe the name of the team in `content` column when inserting `comment` into DB in case that we cannot get the name of team after it is deleted. But for comments that already exist, just display "Unknown Team"~~ Just display "Ghost Team" in the comment if the assgined team is deleted. - [x] 2. Delete the PR&team binding (the row of which `review_team_id = ${team_id} ` in table `review`) when deleting team. - [x] 3.For already exist and undeleted binding rows in in table `review`, ~~we can delete these rows when executing migrations.~~ they do not affect the function, so won't delete them.		2023-04-19 19:50:00 -04:00
..
fields
labels
view_content	Fix internal sever error when visiting a PR that bound to the deleted team (#24127)	2023-04-19 19:50:00 -04:00
branch_selector_field.tmpl
choose.tmpl
comment_tab.tmpl
label_precolors.tmpl
labels.tmpl
list.tmpl
milestone_issues.tmpl
milestone_new.tmpl
milestones.tmpl
navbar.tmpl
new_form.tmpl
new.tmpl
openclose.tmpl
search.tmpl
view_content.tmpl
view_title.tmpl
view.tmpl