mirror of
https://codeberg.org/forgejo/forgejo
synced 2024-12-03 15:26:14 +01:00
aaa1094663
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> |
||
|---|---|---|
| .. | ||
| fields | ||
| labels | ||
| milestone | ||
| view_content | ||
| branch_selector_field.tmpl | ||
| choose.tmpl | ||
| comment_tab.tmpl | ||
| label_precolors.tmpl | ||
| labels.tmpl | ||
| list.tmpl | ||
| milestone_issues.tmpl | ||
| milestone_new.tmpl | ||
| milestones.tmpl | ||
| navbar.tmpl | ||
| new.tmpl | ||
| new_form.tmpl | ||
| openclose.tmpl | ||
| search.tmpl | ||
| view.tmpl | ||
| view_content.tmpl | ||
| view_title.tmpl | ||
