sillyguodong 2f49b55c19 Fix cannot reopen after pushing commits to a closed PR (#23189) ... Close: #22784 1. On GH, we can reopen a PR which was closed before after pushing commits. After reopening PR, we can see the commits that were pushed after closing PR in the time line. So the case of [issue](https://github.com/go-gitea/gitea/issues/22784) is a bug which needs to be fixed. 2. After closing a PR and pushing commits, `headBranchSha` is not equal to `sha`(which is the last commit ID string of reference). If the judgement exists, the button of reopen will not display. So, skip the judgement if the status of PR is closed.  3. Even if PR is already close, we should still insert comment record into DB when we push commits. So we should still call function `CreatePushPullComment()`. 067b0c2664/services/pull/pull.go (L260-L282) So, I add a switch(`includeClosed`) to the `GetUnmergedPullRequestsByHeadInfo` func to control whether the status of PR must be open. In this case, by setting `includeClosed` to `true`, we can query the closed PR.  4. In the loop of comments, I use the`latestCloseCommentID` variable to record the last occurrence of the close comment. In the go template, if the status of PR is closed, the comments whose type is `CommentTypePullRequestPush(29)` after `latestCloseCommentID` won't be rendered.  e.g. 1). The initial status of the PR is opened.  2). Then I click the button of `Close`. PR is closed now.  3). I try to push a commit to this PR, even though its current status is closed.  But in comments list, this commit do not display.This is as expected ：）  4). Click the `Reopen` button, the commit which is pushed after closing PR display now.  --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>		2023-03-03 21:16:58 +08:00
..
actions	Avoid too long names for actions (#23162)	2023-02-28 18:20:36 +08:00
activities	Add pagination for dashboard and user activity feeds (#22937)	2023-02-24 16:15:10 -05:00
admin	…
asymkey	Refactor the setting to make unit test easier (#22405)	2023-02-20 00:12:01 +08:00
auth	Use minio/sha256-simd for accelerated SHA256 (#23052)	2023-02-22 14:21:46 -05:00
avatars	Avoid warning for system setting when start up (#23054)	2023-02-24 18:23:13 +08:00
db	Fix db.Find bug (#23115)	2023-02-24 21:17:09 +08:00
dbfs	Refactor the setting to make unit test easier (#22405)	2023-02-20 00:12:01 +08:00
fixtures	Use correct README link to render the README (#23152)	2023-03-03 18:01:33 +08:00
git	Rename `repo.GetOwner` to `repo.LoadOwner` (#22967)	2023-02-18 20:11:03 +08:00
issues	Fix cannot reopen after pushing commits to a closed PR (#23189)	2023-03-03 21:16:58 +08:00
migrations	Require approval to run actions for fork pull request (#22803)	2023-02-24 15:58:49 +08:00
organization	Rename `GetUnits` to `LoadUnits` (#22970)	2023-02-19 16:31:39 +08:00
packages	…
perm	Rename `repo.GetOwner` to `repo.LoadOwner` (#22967)	2023-02-18 20:11:03 +08:00
project	improve FindProjects (#23085)	2023-02-24 13:18:52 +08:00
pull	…
repo	Rename `repo.GetOwner` to `repo.LoadOwner` (#22967)	2023-02-18 20:11:03 +08:00
secret	…
system	Avoid warning for system setting when start up (#23054)	2023-02-24 18:23:13 +08:00
unit	…
unittest	Avoid warning for system setting when start up (#23054)	2023-02-24 18:23:13 +08:00
user	Avoid warning for system setting when start up (#23054)	2023-02-24 18:23:13 +08:00
webhook	…
error.go	…
fixture_generation.go	…
fixture_test.go	…
main_test.go	Refactor the setting to make unit test easier (#22405)	2023-02-20 00:12:01 +08:00
migrate.go	…
migrate_test.go	…
org.go	…
org_team.go	…
org_team_test.go	…
org_test.go	…
repo.go	Avoid warning for system setting when start up (#23054)	2023-02-24 18:23:13 +08:00
repo_collaboration.go	…
repo_collaboration_test.go	Rename `repo.GetOwner` to `repo.LoadOwner` (#22967)	2023-02-18 20:11:03 +08:00
repo_test.go	…
repo_transfer.go	…
repo_transfer_test.go	…