gitea/services/issue
Lunny Xiao 5feb1a6bff
Use `CloseIssue` and `ReopenIssue` instead of `ChangeStatus` ()
The behaviors of closing issues and reopening issues are very different.
So splitting it into two different functions makes it easier to
maintain.

- [x] Split ChangeIssueStatus into CloseIssue and ReopenIssue both at
the service layer and model layer
- [x] Rename `isClosed` to `CloseOrReopen` to make it more readable.
- [x] Add transactions for ReopenIssue and CloseIssue

---------

Co-authored-by: Zettat123 <zettat123@gmail.com>
..
assignee.go Fix get reviewers' bug ()
assignee_test.go Performance improvements for pull request list API ()
comments.go Prevent simultaneous editing of comments and issues ()
commit.go Use `CloseIssue` and `ReopenIssue` instead of `ChangeStatus` ()
commit_test.go Replace 'userxx' with 'orgxx' in all test files when the user type is org ()
content.go Prevent simultaneous editing of comments and issues ()
issue.go Issue time estimate, meaningful time tracking ()
issue_test.go Penultimate round of `db.DefaultContext` refactor ()
label.go Penultimate round of `db.DefaultContext` refactor ()
label_test.go Next round of `db.DefaultContext` refactor ()
main_test.go Move AddCollabrator and CreateRepositoryByExample to service layer ()
milestone.go demilestone should not include milestone ()
milestone_test.go demilestone should not include milestone ()
pull.go Update misspell to 0.5.1 and add `misspellings.csv` ()
reaction.go Add user blocking ()
reaction_test.go Add user blocking ()
status.go Use `CloseIssue` and `ReopenIssue` instead of `ChangeStatus` ()
template.go refactor: remove redundant err declarations ()