github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

"Comment and close" replaces first issue comment with last comment #1082

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

Originally created by @mxmehl on GitHub (Sep 19, 2017).

Description

This is a very severe bug because is modifies issues and potentially important information!

In an open issue, when clicking "comment and close", the text of the closing comment replaces the text of the first comment in this issue (fortunately not those in between).

Examples: https://try.gitea.io/mxmehl/test1/issues/1 or https://git.fsfe.org/pmpc/website/issues/89

Originally created by @mxmehl on GitHub (Sep 19, 2017). - Gitea version (or commit ref): d155d0e - Git version: 2.1.4 - Operating system: Debian 8 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL): https://try.gitea.io/mxmehl/test1/issues/1 - [ ] No - [ ] Not relevant - Log gist: ## Description This is a very severe bug because is modifies issues and potentially important information! In an open issue, when clicking "comment and close", the text of the closing comment replaces the text of the first comment in this issue (*fortunately* not those in between). Examples: https://try.gitea.io/mxmehl/test1/issues/1 or https://git.fsfe.org/pmpc/website/issues/89
GiteaMirror added the type/bug label 2025-11-02 03:47:39 -06:00
GiteaMirror commented 2025-11-02 03:47:41 -06:00
Author
Owner
Copy Link

@mxmehl commented on GitHub (Sep 19, 2017):

This has already been the case with commit b0f7457, the version we had running before, but not with 5f4210a

@mxmehl commented on GitHub (Sep 19, 2017): This has already been the case with commit b0f7457, the version we had running before, but not with 5f4210a
GiteaMirror commented 2025-11-02 03:47:41 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 20, 2017):

Not present in 1.2.0-rc2 only on master branch

@lafriks commented on GitHub (Sep 20, 2017): Not present in 1.2.0-rc2 only on master branch
GiteaMirror commented 2025-11-02 03:47:41 -06:00
Author
Owner
Copy Link

@mxmehl commented on GitHub (Sep 20, 2017):

The bug also happens when reopening an issue with a comment.

Does anyone have an idea how this could have been caused in the latest commits?

@mxmehl commented on GitHub (Sep 20, 2017): The bug also happens when reopening an issue with a comment. Does anyone have an idea how this could have been caused in the latest commits?
GiteaMirror commented 2025-11-02 03:47:41 -06:00
Author
Owner
Copy Link

@mxmehl commented on GitHub (Sep 21, 2017):

Workaround: Comment on an issue, and close it in a second step. Then the first message isn't overwritten. But who does it this way if there's a shortcut?

@mxmehl commented on GitHub (Sep 21, 2017): Workaround: Comment on an issue, and close it in a second step. Then the first message isn't overwritten. But who does it this way if there's a shortcut?
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
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#1082
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?