New feature: Improved release type download configuration #184

New Issue

2026-10-27T12:09:56+01:00

adam commented

2026-10-27 12:09:56 +01:00

Hi,

after having some repos on my watchlist (around 300 right now)

Some of them are downloading pre-releases (to often) which is not that necessary for me. Thats why I improved the release configuration.

Here some screenshots about this integration:

The same exists for organizations as well.

This implementation is almost ready to go, but I have to wait for my other "small" notification settings release, cause both have the same base branch (not jet committed).

Just a note, if you see something upfront.

Cheers
Floh

Hi, after having some repos on my watchlist (around 300 right now) Some of them are downloading pre-releases (to often) which is not that necessary for me. Thats why I improved the release configuration. Here some screenshots about this integration: <img width="1659" height="710" alt="Image" src="https://github.com/user-attachments/assets/96819f8d-5d73-46d2-b6c7-77b7271125c5" /> <img width="589" height="387" alt="Image" src="https://github.com/user-attachments/assets/6925222e-495b-460f-90c1-d7f0e73061c5" /> <img width="803" height="1093" alt="Image" src="https://github.com/user-attachments/assets/645a649b-8f39-4845-923e-7d100ff28b80" /> <img width="804" height="1398" alt="Image" src="https://github.com/user-attachments/assets/54ffd1e4-d9b3-4438-8f7d-117b81796ed1" /> The same exists for organizations as well. This implementation is almost ready to go, but I have to wait for my other "small" notification settings release, cause both have the same base branch (not jet committed). Just a note, if you see something upfront. Cheers Floh

adam closed this issue

2026-10-27 12:09:56 +01:00

adam commented

2026-10-27 12:09:57 +01:00

Hey @MajMcCloud, thanks for the heads up! Skipping pre-releases makes total sense, and I'd like to have it. I just think the UI can be a lot lighter, so I mocked up what I have in mind:

The idea is a simple default with the custom stuff out of the way. "Pre-releases" is one switch that just uses GitHub's pre-release flag, which covers most repos. For repos that publish RCs as normal releases or have their own naming, there's a "Custom tag rules" link that opens a small dialog with your include and exclude boxes. A badge next to the link shows when rules are set, so they don't get forgotten. The "Try it on" preview shows which tags of a repo would be kept or skipped before saving, since a typo in a pattern would otherwise delete releases on the next sync.

In the repo and org dialog there's no second tab. The Releases dropdown gets a "Stable only" option, and the same rules sit in a collapsed section there, since a dialog inside a dialog felt clunky.

One thing on the code side. A pattern that matches nothing would page through every release of every repo, so a page cap with a log line would help.

Cheers!

Hey @MajMcCloud, thanks for the heads up! Skipping pre-releases makes total sense, and I'd like to have it. I just think the UI can be a lot lighter, so I mocked up what I have in mind: ![Global settings](https://gist.githubusercontent.com/arunavo4/5c5a463870d81fd5fd474847ca5c287a/raw/37f538e042521b5613d339c8a09ceab188a4bd86/global.png) ![Custom tag rules dialog](https://gist.githubusercontent.com/arunavo4/5c5a463870d81fd5fd474847ca5c287a/raw/37f538e042521b5613d339c8a09ceab188a4bd86/rules-dialog.png) ![Repository dialog](https://gist.githubusercontent.com/arunavo4/5c5a463870d81fd5fd474847ca5c287a/raw/37f538e042521b5613d339c8a09ceab188a4bd86/dialog.png) The idea is a simple default with the custom stuff out of the way. "Pre-releases" is one switch that just uses GitHub's pre-release flag, which covers most repos. For repos that publish RCs as normal releases or have their own naming, there's a "Custom tag rules" link that opens a small dialog with your include and exclude boxes. A badge next to the link shows when rules are set, so they don't get forgotten. The "Try it on" preview shows which tags of a repo would be kept or skipped before saving, since a typo in a pattern would otherwise delete releases on the next sync. In the repo and org dialog there's no second tab. The Releases dropdown gets a "Stable only" option, and the same rules sit in a collapsed section there, since a dialog inside a dialog felt clunky. One thing on the code side. A pattern that matches nothing would page through every release of every repo, so a page cap with a log line would help. Cheers!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/gitea-mirror#184