Target branch filter for Pull Requests #11397

New Issue

GiteaMirror · 2025-11-02T09:36:32-06:00

GiteaMirror commented

2025-11-02 09:36:32 -06:00

Originally created by @tpiekarski on GitHub (Aug 3, 2023).

Feature Description

The possibility to filter pull requests by target branch would be a great feature for gitea (see mockup).

Screenshots

Originally created by @tpiekarski on GitHub (Aug 3, 2023). ### Feature Description The possibility to filter pull requests by target branch would be a great feature for gitea (see mockup). ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/5697640/60baa56d-334a-4a60-8367-d8135d3429ae)

GiteaMirror added the type/proposal label 2025-11-02 09:36:32 -06:00

GiteaMirror commented

2025-11-02 09:36:33 -06:00

@puni9869 commented on GitHub (Aug 3, 2023):

You can use the label. It will be redundant to have a branch filter.

@puni9869 commented on GitHub (Aug 3, 2023): You can use the label. It will be redundant to have a branch filter.

GiteaMirror commented

2025-11-02 09:36:33 -06:00

@wolfogre commented on GitHub (Aug 4, 2023):

I don't think it's redundant. Let's take Gitea itself as an example, sometimes I want to filter out PRs which are not backports.

I can do that by:

@wolfogre commented on GitHub (Aug 4, 2023): I don't think it's redundant. Let's take Gitea itself as an example, sometimes I want to filter out PRs which are not backports. I can do that by: <img width="1252" alt="image" src="https://github.com/go-gitea/gitea/assets/9418365/93519c42-a2cf-4b88-976d-b09c9d6718d3">

GiteaMirror commented

2025-11-02 09:36:33 -06:00

@lunny commented on GitHub (Aug 4, 2023):

More and more filters, we really need a search syntax like GH's

@lunny commented on GitHub (Aug 4, 2023): More and more filters, we really need a search syntax like GH's

GiteaMirror commented

2025-11-02 09:36:33 -06:00

@puni9869 commented on GitHub (Aug 4, 2023):

Agree with @lunny

@puni9869 commented on GitHub (Aug 4, 2023): Agree with @lunny

GiteaMirror commented

2025-11-02 09:36:34 -06:00

@tpiekarski commented on GitHub (Aug 4, 2023):

You can use the label. It will be redundant to have a branch filter.

No. How should I use labels? How is such filter redundant? Should I label every PR and the label contain the target branch name?

Now that's redundant. Every PR has the source and target branch already.

Well, look around. Github and gitlab got such filter, so I think they're useful 😊

If you want I can take a closer look and draft a PR.

@tpiekarski commented on GitHub (Aug 4, 2023): > You can use the label. It will be redundant to have a branch filter. No. How should I use labels? How is such filter redundant? Should I label every PR and the label contain the target branch name? Now that's redundant. Every PR has the source and target branch already. Well, look around. Github and gitlab got such filter, so I think they're useful 😊 If you want I can take a closer look and draft a PR.

GiteaMirror commented

2025-11-02 09:36:34 -06:00

@puni9869 commented on GitHub (Aug 5, 2023):

Pr is always welcome. But before that I would like the see the how you will implement. A small work flow or approach before you start.
Currently

Github is having query parser.
Gitlab is having enrich tag based query.

You have my full support on this feature.

@puni9869 commented on GitHub (Aug 5, 2023): Pr is always welcome. But before that I would like the see the how you will implement. A small work flow or approach before you start. Currently 1. Github is having query parser. 2. Gitlab is having enrich tag based query. You have my full support on this feature.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11397