Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow to specify branch masks to exclude from recently pused branch notifications #28447

Closed
lafriks opened this issue Dec 12, 2023 · 2 comments
Closed

Allow to specify branch masks to exclude from recently pused branch notifications #28447

lafriks opened this issue Dec 12, 2023 · 2 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@lafriks
Copy link
Member

lafriks commented Dec 12, 2023

Feature Description

Currently if there are multiple branches that are never merged into default, like release/* etc pushing changes to them shows recent branch notification with button to create new PR for 6 hours that takes up quite much space for whole working day.

There could be two ways to implemented this:

  1. do not show notifications for branches that are protected (like when setting branch protection for release/* would not show notification to create PR for these branches)
  2. Allow to specify global (app.ini) setting with wildcard to what branches always ignore for this notification, for example main,release/*

Screenshots

No response
@lafriks lafriks added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Dec 12, 2023
@lafriks lafriks changed the title Allow to specify branch masks to exclud from recently pused branch notifications Allow to specify branch masks to exclud3 from recently pused branch notifications Dec 12, 2023
@lafriks lafriks changed the title Allow to specify branch masks to exclud3 from recently pused branch notifications Allow to specify branch masks to exclude from recently pused branch notifications Dec 12, 2023
This was referenced Aug 1, 2024
Closed
Merged
@lafriks
Copy link
Member Author

lafriks commented Aug 1, 2024

Fixed in #31748

@lafriks lafriks closed this as completed Aug 1, 2024
@wolfogre
Copy link
Member

wolfogre commented Aug 1, 2024

👍 Oh right, it can be done by just protecting branches.

@go-gitea go-gitea locked as resolved and limited conversation to collaborators Oct 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lafriks @wolfogre