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

Commenting and closing an issue at the same time button #4938

New Issue
Closed
opened 2025-11-02 06:08:18 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 06:08:18 -06:00
Owner
Copy Link

Originally created by @aha999 on GitHub (Feb 26, 2020).

www.codeberg.org uses Gitea so i thought i can comment here on the issue.
When you want to make a comment and close the issue with that, there's only "close" next to the comment button. I think it would be better if the option was renamed to "comment & close" so we know it's going to post a comment and then close the issue (if there is text in the comment field already). Or maybe have three options.
With only Close option some can get confused if it's going to comment and then close, or just close.

DCDZw94595

Github method:
A7Q67sS68H

Originally created by @aha999 on GitHub (Feb 26, 2020). www.codeberg.org uses Gitea so i thought i can comment here on the issue. When you want to make a comment and close the issue with that, there's only "close" next to the comment button. I think it would be better if the option was renamed to "comment & close" so we know it's going to post a comment and then close the issue (if there is text in the comment field already). Or maybe have three options. With only Close option some can get confused if it's going to comment and then close, or just close. ![DCDZw94595](https://user-images.githubusercontent.com/50620416/75304130-def67100-5842-11ea-9eea-a19f7e0aa076.png) Github method: ![A7Q67sS68H](https://user-images.githubusercontent.com/50620416/75351082-d1bf9d80-58a7-11ea-81ef-6dd3d928383f.gif)
GiteaMirror added the topic/uitype/proposal labels 2025-11-02 06:08:18 -06:00
GiteaMirror commented 2025-11-02 06:08:19 -06:00
Author
Owner
Copy Link

@JVimes commented on GitHub (Feb 24, 2023):

@guillep2k #14407 says this feature exists. This might be "bug fix" instead of proposal?

@JVimes commented on GitHub (Feb 24, 2023): @guillep2k #14407 says this feature exists. This might be "bug fix" instead of proposal?
GiteaMirror commented 2025-11-02 06:08:19 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 25, 2023):

Not a bug fix, but the missing code for new editor, the new editor didn't support that .....

Will be fixed by #23135

@wxiaoguang commented on GitHub (Feb 25, 2023): ~~Not a bug fix~~, but the missing code for new editor, the new editor didn't support that ..... Will be fixed by #23135
GiteaMirror commented 2025-11-02 06:08:19 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Feb 25, 2023):

@guillep2k #14407 says this feature exists. This might be "bug fix" instead of proposal?

Ha! Is time going backwards?

@guillep2k commented on GitHub (Feb 25, 2023): > @guillep2k #14407 says this feature exists. This might be "bug fix" instead of proposal? Ha! Is time going backwards?
GiteaMirror commented 2025-11-02 06:08:20 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 25, 2023):

The "existing" feature for rich editor is a hacky patch, it doesn't work well with real rich editors, so it got broken later.

EasyMDE/CodeMirror need to handle the onChange event.

@wxiaoguang commented on GitHub (Feb 25, 2023): The "existing" feature for rich editor is a hacky patch, it doesn't work well with real rich editors, so it got broken later. EasyMDE/CodeMirror need to handle the `onChange` event.
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 topic/ui 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#4938
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?