JakobDev aaa1094663 Add the ability to pin Issues (#24406) ... This adds the ability to pin important Issues and Pull Requests. You can also move pinned Issues around to change their Position. Resolves #2175. ## Screenshots    The Design was mostly copied from the Projects Board. ## Implementation This uses a new `pin_order` Column in the `issue` table. If the value is set to 0, the Issue is not pinned. If it's set to a bigger value, the value is the Position. 1 means it's the first pinned Issue, 2 means it's the second one etc. This is dived into Issues and Pull requests for each Repo. ## TODO - [x] You can currently pin as many Issues as you want. Maybe we should add a Limit, which is configurable. GitHub uses 3, but I prefer 6, as this is better for bigger Projects, but I'm open for suggestions. - [x] Pin and Unpin events need to be added to the Issue history. - [x] Tests - [x] Migration **The feature itself is currently fully working, so tester who may find weird edge cases are very welcome!** --------- Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: Giteabot <teabot@gitea.io>		2023-05-25 15:17:19 +02:00
..
assignees_test.go
assignees.go
comment_code.go
comment_list.go
comment_test.go
comment.go	Add the ability to pin Issues (#24406)	2023-05-25 15:17:19 +02:00
content_history_test.go
content_history.go
dependency_test.go
dependency.go
issue_index.go
issue_label.go
issue_list_test.go
issue_list.go
issue_lock.go
issue_project.go
issue_search.go
issue_stats.go
issue_test.go
issue_update.go
issue_user_test.go
issue_user.go
issue_watch_test.go
issue_watch.go
issue_xref_test.go
issue_xref.go
issue.go	Add the ability to pin Issues (#24406)	2023-05-25 15:17:19 +02:00
label_test.go
label.go
main_test.go
milestone_test.go
milestone.go
pull_list.go
pull_test.go
pull.go
reaction_test.go
reaction.go
review_test.go
review.go
stopwatch_test.go
stopwatch.go
tracked_time_test.go
tracked_time.go