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

Issue with Pull Request: Changes Not Reflected When Creating PR from Development to Main Branch #14855

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

Originally created by @Kumaresansyncfusion on GitHub (Aug 12, 2025).

Description

Description:

  1. We are experiencing issues when creating a pull request from the development branch to the main branch. Specifically:
  2. We committed changes to the main branch directly.
  3. These changes are already present in the main branch.
  4. When attempting to create a new pull request, the changes are not reflected correctly.
  5. The pull request shows differences in commit history, even though the changes are already in the main branch.

Steps to reproduce

  1. Create a repository with main and development branches
  2. Make changes in main branch
  3. Make same changes in development branch
  4. Commit and push changes
  5. Create a pull request from development to main
  6. Notice the diff does not reflect recent changes

Gitea Version

1.24.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Image Image

Git Version

2.49.1

Operating System

No response

How are you running Gitea?

Docker

Database

PostgreSQL

Originally created by @Kumaresansyncfusion on GitHub (Aug 12, 2025). ### Description Description: 1. We are experiencing issues when creating a pull request from the development branch to the main branch. Specifically: 2. We committed changes to the main branch directly. 3. These changes are already present in the main branch. 4. When attempting to create a new pull request, the changes are not reflected correctly. 5. The pull request shows differences in commit history, even though the changes are already in the main branch. Steps to reproduce 1. Create a repository with main and development branches 2. Make changes in main branch 3. Make same changes in development branch 4. Commit and push changes 5. Create a pull request from development to main 6. Notice the diff does not reflect recent changes ### Gitea Version 1.24.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots <img width="1893" height="757" alt="Image" src="https://github.com/user-attachments/assets/623684f1-3705-4d84-abc1-a947302a9c68" /> <img width="1304" height="384" alt="Image" src="https://github.com/user-attachments/assets/764dd284-568f-4e0a-a301-9d3f49cd2e35" /> ### Git Version 2.49.1 ### Operating System _No response_ ### How are you running Gitea? Docker ### Database PostgreSQL
GiteaMirror added the topic/prtype/bug labels 2025-11-02 11:24:30 -06:00
GiteaMirror commented 2025-11-02 11:24:32 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 13, 2025):

Could you reproduce it in https://demo.gitea.com or https://gitea.com ?

@lunny commented on GitHub (Aug 13, 2025): Could you reproduce it in https://demo.gitea.com or https://gitea.com ?
GiteaMirror commented 2025-11-02 11:24:32 -06:00
Author
Owner
Copy Link

@Kumaresansyncfusion commented on GitHub (Aug 14, 2025):

Hi @lunny
I have created new PR in demo site - https://gitea.com/TestingPR/Pr-issues-check/pulls/1/files
Changes are already present in target branch ,when creating PR from development to main branch its shows in difference
main branch -https://gitea.com/TestingPR/Pr-issues-check/src/branch/main/

@Kumaresansyncfusion commented on GitHub (Aug 14, 2025): Hi @lunny I have created new PR in demo site - https://gitea.com/TestingPR/Pr-issues-check/pulls/1/files Changes are already present in target branch ,when creating PR from development to main branch its shows in difference main branch -https://gitea.com/TestingPR/Pr-issues-check/src/branch/main/
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/pr 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#14855
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?