1
0
Fork 0
forgejo/services/issue
Lunny Xiao 184a7d4195
Check if project has the same repository id with issue when assign project to issue (#20133)
* Check if project has the same repository id with issue when assign project to issue

* Check if issue's repository id match project's repository id

* Add more permission checking

* Remove invalid argument

* Fix errors

* Add generic check

* Remove duplicated check

* Return error + add check for new issues

* Apply suggestions from code review

Co-authored-by: KN4CK3R <admin@oldschoolhack.me>

Co-authored-by: Gusted <williamzijl7@hotmail.com>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: 6543 <6543@obermui.de>
2022-06-30 23:55:08 +08:00
..
assignee.go Add more linters to improve code readability (#19989) 2022-06-20 12:02:49 +02:00
assignee_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
commit.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
commit_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
content.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
issue.go Add more linters to improve code readability (#19989) 2022-06-20 12:02:49 +02:00
issue_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
label.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
label_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
main_test.go Use a struct as test options (#19393) 2022-04-14 21:58:21 +08:00
milestone.go Check if project has the same repository id with issue when assign project to issue (#20133) 2022-06-30 23:55:08 +08:00
milestone_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
status.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00