github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

PR shows unrelated commits after merge #1279

New Issue
Closed
opened 2025-11-02 03:55:16 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 03:55:16 -06:00
Owner
Copy Link

Originally created by @mxmehl on GitHub (Nov 26, 2017).

  • Gitea version (or commit ref): 1.2.3
  • Git version: 2.1.4
  • Operating system: Debian 8
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After I merged Pull Requests, the PR page sometimes shows commits which are completely unrelated to what the PR has been about. It seems to include commits which happened between creating the branch/PR and the actual merge.

As an example, please see PR 29 on my installation by the user fbn_bmns which consisted of exactly one commit. After merging it, it shows 22 commits in total!

Why is this happening? Is this a Gitea bug? It would be good to have this fixed as it disables us having a decent overview about what happened in a PR after it has been merged...

Originally created by @mxmehl on GitHub (Nov 26, 2017). - Gitea version (or commit ref): 1.2.3 - 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: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description After I merged Pull Requests, the PR page sometimes shows commits which are completely unrelated to what the PR has been about. It seems to include commits which happened between creating the branch/PR and the actual merge. As an example, please see [PR 29](https://git.fsfe.org/FSFE/fsfe-website/pulls/29) on my installation by the user fbn_bmns which consisted of exactly [one commit](https://git.fsfe.org/FSFE/fsfe-website/commit/c35aafe3566c53d93bf5baf2520fc159f602161c). After merging it, it shows [22 commits](https://git.fsfe.org/FSFE/fsfe-website/pulls/29/commits) in total! Why is this happening? Is this a Gitea bug? It would be good to have this fixed as it disables us having a decent overview about what happened in a PR after it has been merged...
GiteaMirror added the issue/duplicate label 2025-11-02 03:55:16 -06:00
GiteaMirror commented 2025-11-02 03:55:17 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 26, 2017):

I believe this is duplicate of #2797 and is already fixed in master and will be fixed also in 1.3.0-rc2 release

@lafriks commented on GitHub (Nov 26, 2017): I believe this is duplicate of #2797 and is already fixed in master and will be fixed also in 1.3.0-rc2 release
GiteaMirror commented 2025-11-02 03:55:17 -06:00
Author
Owner
Copy Link

@mxmehl commented on GitHub (Nov 26, 2017):

You are right, this looks like my problem. Please excuse the duplicate, I didn't find this via the search.

@mxmehl commented on GitHub (Nov 26, 2017): You are right, this looks like my problem. Please excuse the duplicate, I didn't find this via the search.
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/duplicate
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#1279
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?