github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Automatically close issues by manually merging a PR #10157

New Issue
Open
opened 2025-11-02 08:59:50 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 08:59:50 -06:00
Owner
Copy Link

Originally created by @jack-wulf on GitHub (Jan 26, 2023).

Feature Description

I would suggest that the issues that are included in the description of a PR with the close keywords should be automatically closed when the PR is manually merged. This behavior is already implemented for automatic merge. I think the same behavior should apply for manual merge.

Screenshots

No response

Originally created by @jack-wulf on GitHub (Jan 26, 2023). ### Feature Description I would suggest that the issues that are included in the description of a PR with the ``close keywords`` should be automatically closed when the PR is manually merged. This behavior is already implemented for automatic merge. I think the same behavior should apply for manual merge. ### Screenshots _No response_
GiteaMirror added the type/featuretype/bug labels 2025-11-02 08:59:50 -06:00
GiteaMirror commented 2025-11-02 08:59:50 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jan 26, 2023):

(I've added the bug label now as I think it is equally a bug and an unimplemented feature:
I see it as unexpected behavior, but also as missing functionality)

@delvh commented on GitHub (Jan 26, 2023): (I've added the `bug` label now as I think it is equally a bug and an unimplemented feature: I see it as unexpected behavior, but also as missing functionality)
GiteaMirror commented 2025-11-02 08:59:50 -06:00
Author
Owner
Copy Link

@JustKato commented on GitHub (Jan 17, 2024):

I can also +1 to this issue, Would love to see it implemented, even though ti has been over a year since this has been reported :/

@JustKato commented on GitHub (Jan 17, 2024): I can also +1 to this issue, Would love to see it implemented, even though ti has been over a year since this has been reported :/
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 type/bug type/feature
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#10157
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?