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

Allow issues to be deleted #2778

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

Originally created by @Larivact on GitHub (Jan 19, 2019).

  • Gitea version (or commit ref): 1.7.0

Description

I think repository owners should be able to delete issues. For example to clean up accidentally created issues. GitHub supports this since November 7, 2018: https://help.github.com/articles/deleting-an-issue/.

Originally created by @Larivact on GitHub (Jan 19, 2019). - Gitea version (or commit ref): 1.7.0 ## Description I think repository owners should be able to delete issues. For example to clean up accidentally created issues. GitHub supports this since November 7, 2018: https://help.github.com/articles/deleting-an-issue/.
GiteaMirror added the type/proposal label 2025-11-02 04:48:11 -06:00
GiteaMirror commented 2025-11-02 04:48:12 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Jan 20, 2019):

Sounds nice...

Looks like I have a handful of PRs to make today 🙏🙏

@adelowo commented on GitHub (Jan 20, 2019): Sounds nice... Looks like I have a handful of PRs to make today 🙏🙏
GiteaMirror commented 2025-11-02 04:48:12 -06:00
Author
Owner
Copy Link

@davydov-vyacheslav commented on GitHub (Jan 21, 2019):

looks like copy of #923 ;)

@davydov-vyacheslav commented on GitHub (Jan 21, 2019): looks like copy of #923 ;)
GiteaMirror commented 2025-11-02 04:48:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 22, 2019):

@techknowlogick but I think site administrators should have abilities to delete issues on admin panel to maintain the site.

@lunny commented on GitHub (Jan 22, 2019): @techknowlogick but I think site administrators should have abilities to delete issues on admin panel to maintain the site.
GiteaMirror commented 2025-11-02 04:48:13 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jan 22, 2019):

@lunny I agree. This issue was closed because it is a duplicate. I kept original open.

@techknowlogick commented on GitHub (Jan 22, 2019): @lunny I agree. This issue was closed because it is a duplicate. I kept original open.
GiteaMirror commented 2025-11-02 04:48:13 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Jan 22, 2019):

@lunny GitHub has it's own on the issues page ( The sidebar). Should I follow that model or use the admin panel as you mentioned.

I hope to work on this during the weekend

@adelowo commented on GitHub (Jan 22, 2019): @lunny GitHub has it's own on the issues page ( The sidebar). Should I follow that model or use the admin panel as you mentioned. > I hope to work on this during the weekend
GiteaMirror commented 2025-11-02 04:48:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 22, 2019):

@adelowo I think admin panel issues management is necessary and github's model could be a configuration that site admin could disable it.

@lunny commented on GitHub (Jan 22, 2019): @adelowo I think admin panel issues management is necessary and github's model could be a configuration that site admin could disable it.
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/proposal
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#2778
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?