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

Forked repository is compared wrong #1217

New Issue
Closed
opened 2025-11-02 03:52:44 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 03:52:44 -06:00
Owner
Copy Link

Originally created by @webjoel on GitHub (Nov 6, 2017).

  • Gitea version (or commit ref): cdc4600
  • Git version: 2.7.4
  • Operating system: Linux 64 Ubuntu
  • 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

Comparison of changes / New Pull request is not comparing the forked repository, but rather the origin repository. (Image 1 and image 2).

When I change the URL manually the "compare" works as expected. (Image 3).

Screenshots

Image 1:
captura de tela de 2017-11-06 15-23-03

Image 2:
captura de tela de 2017-11-06 14-49-42

Image 3:
captura de tela de 2017-11-06 14-49-34

Originally created by @webjoel on GitHub (Nov 6, 2017). - Gitea version (or commit ref): cdc4600 - Git version: 2.7.4 - Operating system: Linux 64 Ubuntu - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Comparison of changes / New Pull request is not comparing the forked repository, but rather the origin repository. (Image 1 and image 2). When I change the URL manually the "compare" works as expected. (Image 3). ## Screenshots Image 1: ![captura de tela de 2017-11-06 15-23-03](https://user-images.githubusercontent.com/1946348/32454910-c3e30590-c307-11e7-8c43-5794498c7989.png) Image 2: ![captura de tela de 2017-11-06 14-49-42](https://user-images.githubusercontent.com/1946348/32454926-cc3f93a2-c307-11e7-8b90-5ed29a984f6b.png) Image 3: ![captura de tela de 2017-11-06 14-49-34](https://user-images.githubusercontent.com/1946348/32454937-d39465ec-c307-11e7-9411-d31a1f8df090.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 03:52:44 -06:00
GiteaMirror commented 2025-11-02 03:52:45 -06:00
Author
Owner
Copy Link

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

@lunny could this be related to your latest changes?

@lafriks commented on GitHub (Nov 6, 2017): @lunny could this be related to your latest changes?
GiteaMirror commented 2025-11-02 03:52:45 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 7, 2017):

@lafriks I will check it.

@lunny commented on GitHub (Nov 7, 2017): @lafriks I will check it.
GiteaMirror commented 2025-11-02 03:52:45 -06:00
Author
Owner
Copy Link

@zxjon22 commented on GitHub (Dec 7, 2017):

I've just come across this myself. I was in a fork and clicked the New Pull Request button and the pull request was created against the original repository, not the fork.

HTML for the New Pull Request button when in the fork looks like this

<a class="ui green button " href="/[original]/Repo/compare/master...jon:master">New Pull Request</a>

... when it should be

<a class="ui green button " href="/[fork]/Repo/compare/master...jon:master">New Pull Request</a>
@zxjon22 commented on GitHub (Dec 7, 2017): I've just come across this myself. I was in a fork and clicked the `New Pull Request` button and the pull request was created against the original repository, not the fork. HTML for the `New Pull Request` button when in the fork looks like this ```html <a class="ui green button " href="/[original]/Repo/compare/master...jon:master">New Pull Request</a> ``` ... when it should be ```html <a class="ui green button " href="/[fork]/Repo/compare/master...jon:master">New Pull Request</a> ```
GiteaMirror commented 2025-11-02 03:52:45 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 9, 2018):

Could not reproduce it on master, I will close this and feel free to reopen it.

@lunny commented on GitHub (Dec 9, 2018): Could not reproduce it on master, I will close this and feel free to reopen it.
GiteaMirror commented 2025-11-02 03:52:45 -06:00
Author
Owner
Copy Link

@webjoel commented on GitHub (Jan 4, 2019):

This can be tested in:

https://try.gitea.io/webjoel/teste2_1

Pressing in button "compare changes" (image 1). Result is comparassion of other repository (origin fork).

Please repon this issue.

@webjoel commented on GitHub (Jan 4, 2019): This can be tested in: https://try.gitea.io/webjoel/teste2_1 Pressing in button "compare changes" (image 1). Result is comparassion of other repository (origin fork). Please repon this issue.
GiteaMirror commented 2025-11-02 03:52:45 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 5, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 5, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 03:52:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 25, 2020):

Is this still a problem?

@lunny commented on GitHub (Jan 25, 2020): Is this still a problem?
GiteaMirror commented 2025-11-02 03:52:46 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 12, 2021):

I think this bug has been solved by me quite a while ago. Therefore I'm closing it.

@zeripath commented on GitHub (Mar 12, 2021): I think this bug has been solved by me quite a while ago. Therefore I'm closing 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 issue/confirmed 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#1217
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?