6 commits

Author	SHA1	Message	Date
Loïc Dachary	92450913a8	fix POST /{username}/{reponame}/{type:issues|pulls}/move_pin ... (cherry picked from commit d97efb777f)	2023-11-26 06:50:26 +01:00
Loïc Dachary	4927e73551	Revert "fix POST /{username}/{reponame}/{type:issues|pulls}/move_pin" ... This reverts commit e9aa373db5.	2023-11-26 06:34:37 +01:00
Loïc Dachary	e9aa373db5	fix POST /{username}/{reponame}/{type:issues|pulls}/move_pin ... (cherry picked from commit 7eda733ed6a22c08a85fdc90deec0c440427cef7)	2023-11-25 08:08:37 +01:00
Giteabot	03cacf971e	Check ctx.Written() for GetActionIssue (#25698) (#25711) ... Backport #25698 by @wolfogre Fix #25697. Just avoid panic, maybe there's another bug to trigger this case. Co-authored-by: Jason Song <i@wolfogre.com>	2023-07-06 21:04:26 +02:00
JakobDev	1b115296d3	Followup to pinned Issues (#24945) ... This addressees some things from #24406 that came up after the PR was merged. Mostly from @delvh. --------- Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: delvh <dev.lh@web.de>	2023-05-30 15:26:51 +00:00
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