github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH is always true #14994

New Issue
Closed
opened 2025-11-02 11:27:35 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 11:27:35 -06:00
Owner
Copy Link

Originally created by @OddMorning on GitHub (Oct 1, 2025).

Description

I'm able to close issues with keywords in commit description even despite DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH is not specified in the config.

Then I added this and it still affects nothing:

[repository]
DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH = false

It seems the option is broken.

I'm not able to reproduce it on the demo site though (it's running 1.26.0+dev-2-g53dfbbb2ee, that might be a reason?)

Gitea Version

1.24.6

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Running from docker on linux

Database

None

Originally created by @OddMorning on GitHub (Oct 1, 2025). ### Description I'm able to close issues with keywords in commit description even despite `DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH` is not specified in the config. Then I added this and it still affects nothing: ``` [repository] DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH = false ``` It seems the option is broken. I'm not able to reproduce it on the demo site though (it's running `1.26.0+dev-2-g53dfbbb2ee`, that might be a reason?) ### Gitea Version 1.24.6 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Running from docker on linux ### Database None
GiteaMirror added the issue/needs-feedback label 2025-11-02 11:27:35 -06:00
GiteaMirror commented 2025-11-02 11:27:35 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 1, 2025):

It is a per-repo setting

Image
@wxiaoguang commented on GitHub (Oct 1, 2025): It is a per-repo setting <img width="1086" height="492" alt="Image" src="https://github.com/user-attachments/assets/1f2f46fd-afd1-4e2b-aaae-815497c57f32" />
GiteaMirror commented 2025-11-02 11:27:36 -06:00
Author
Owner
Copy Link

@pratyush2514 commented on GitHub (Oct 2, 2025):

please assign me this issue to work one, I'd be happy to contribute on it

@pratyush2514 commented on GitHub (Oct 2, 2025): please assign me this issue to work one, I'd be happy to contribute on it
GiteaMirror commented 2025-11-02 11:27:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 2, 2025):

please assign me this issue to work one, I'd be happy to contribute on it

I don't think you have understood the problem or you know how to work on it. Nothing is broken.

@wxiaoguang commented on GitHub (Oct 2, 2025): > please assign me this issue to work one, I'd be happy to contribute on it I don't think you have understood the problem or you know how to work on it. Nothing is broken.
GiteaMirror commented 2025-11-02 11:27:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 3, 2025):

It is a per-repo setting

@OddMorning does it explain the root cause? And we can close this as "completed"?

@wxiaoguang commented on GitHub (Oct 3, 2025): > It is a per-repo setting @OddMorning does it explain the root cause? And we can close this as "completed"?
GiteaMirror commented 2025-11-02 11:27:36 -06:00
Author
Owner
Copy Link

@OddMorning commented on GitHub (Oct 3, 2025):

It is a per-repo setting

@OddMorning does it explain the root cause? And we can close this as "completed"?

I didn't notice that option, for some reason is was enabled in my repo. Unchecked it and everything is working as expected. So, as you said, nothing is broken.

@OddMorning commented on GitHub (Oct 3, 2025): > > It is a per-repo setting > > [@OddMorning](https://github.com/OddMorning) does it explain the root cause? And we can close this as "completed"? I didn't notice that option, for some reason is was enabled in my repo. Unchecked it and everything is working as expected. So, as you said, nothing is broken.
GiteaMirror commented 2025-11-02 11:27:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 3, 2025):

Yep, DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH means the default value for a new repo creation. It doesn't affect existing repo settings.

@wxiaoguang commented on GitHub (Oct 3, 2025): Yep, `DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH` means the default value for a new repo creation. It doesn't affect existing repo settings.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14994
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?