mirrors
/
forgejo
mirror of
1
Fork 0
Code Issues Releases Activity
forgejo/release-notes/8.0.0/4139.md

6 lines
208 B
Markdown
Raw Normal View History

Reorder repo tabs (#4139) More info in the linked PR. --- Make positioning of the repo tabs make more sense. This is an isolated implementation for one of many changes discussed in the referenced issue, it will work good without the other changes too. ## Changes - Actions are moved to the edge. This tab is the least relevant to both visitors and developers. The first don't really need it at all, the second only visit it when something goes unexpected (run did not happen or attached to the wrong event), or just to see the run queue to know when their actions is going to get processed. This is not a tab with always-relevant information. - put Packages after releases. The Packages are like a download page for Releases, but for released packages instead of binaries/source code. It is relevant to Releases, so it should stay close, but it is secondary to Releases by importance. For example, because they don't actually contain release notes unlike Releases. - the above makes Projects appear next to Issues and Pull requests which I think is nice as they're related. ## Preview ### v7 https://codeberg.org/attachments/c434e8fd-aaab-4c27-9071-2a3ba68ad4b7 ### This PR https://codeberg.org/attachments/74743c03-883e-40cf-8cb1-384d1d8cf63c Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4139 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Reviewed-by: Otto <otto@codeberg.org> Reviewed-by: Beowulf <beowulf@noreply.codeberg.org>
2024-06-16 14:36:41 +02:00
Reorder repo tabs for better UX:
- Actions is now the last tab
- Packages are located after Releases
- This puts Projects after Pull requests
(tab positions may depend on which units are enabled in the repo)