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
..
actions
setting
activity.go
attachment.go
blame.go
branch.go	Improve RSS (#24335)	2023-04-25 22:53:44 -04:00
cherry_pick.go
commit.go
compare.go
download.go
editor.go
editor_test.go
find.go
helper.go
helper_test.go
http.go
http_test.go
issue.go
issue_content_history.go
issue_dependency.go
issue_label.go
issue_label_test.go
issue_lock.go
issue_pin.go
issue_stopwatch.go
issue_test.go
issue_timetrack.go
issue_watch.go
lfs.go
main_test.go
middlewares.go
migrate.go
milestone.go
packages.go
patch.go
projects.go
projects_test.go
pull.go
pull_review.go
release.go
release_test.go
render.go
repo.go
search.go
setting.go
setting_protected_branch.go
settings_test.go
tag.go
topic.go
treelist.go
view.go
view_test.go
webhook.go
wiki.go
wiki_test.go