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

New commits are not being displayed in pull request #6139

New Issue
Closed
opened 2025-11-02 06:46:10 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 06:46:10 -06:00
Owner
Copy Link

Originally created by @lakostin on GitHub (Oct 13, 2020).

  • Gitea version (or commit ref):
    1.13.0+dev-683-gb725c4ee5
  • Git version:
    2.26.2
  • Operating system:
    Alpine Linux
  • 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 adding new commits to the branch with open pull request new commits sometimes do not appear in this pull request.

steps to reproduce:
git checkout master
git pull
git checkout feature_branch
git merge master
git commit -a -m "resolved merge conflict"
git push

...

Screenshots

Screenshot from 2020-10-13 14-54-36
Screenshot from 2020-10-13 14-54-24

Originally created by @lakostin on GitHub (Oct 13, 2020). - Gitea version (or commit ref): 1.13.0+dev-683-gb725c4ee5 - Git version: 2.26.2 - Operating system: Alpine Linux - 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 After adding new commits to the branch with open pull request new commits sometimes do not appear in this pull request. steps to reproduce: git checkout master git pull git checkout feature_branch git merge master git commit -a -m "resolved merge conflict" git push ... ## Screenshots ![Screenshot from 2020-10-13 14-54-36](https://user-images.githubusercontent.com/29179059/95857992-0fa10180-0d65-11eb-938a-728eb9671097.png) ![Screenshot from 2020-10-13 14-54-24](https://user-images.githubusercontent.com/29179059/95857993-10399800-0d65-11eb-92fa-2ed61d17c938.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 06:46:10 -06:00
GiteaMirror commented 2025-11-02 06:46:11 -06:00
Author
Owner
Copy Link

@melmus commented on GitHub (Oct 23, 2020):

I have this problem on my gitea host too.

@melmus commented on GitHub (Oct 23, 2020): I have this problem on my gitea host too.
GiteaMirror commented 2025-11-02 06:46:11 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 23, 2020):

The list of commits is the result of git log pr-branch...pr-base - not from when the pr was created.

@zeripath commented on GitHub (Oct 23, 2020): The list of commits is the result of git log pr-branch...pr-base - not from when the pr was created.
GiteaMirror commented 2025-11-02 06:46:11 -06:00
Author
Owner
Copy Link

@lakostin commented on GitHub (Oct 23, 2020):

The list of commits is the result of git log pr-branch...pr-base - not from when the pr was created.

@zeripath could you explain please what you mean

@lakostin commented on GitHub (Oct 23, 2020): > The list of commits is the result of git log pr-branch...pr-base - not from when the pr was created. @zeripath could you explain please what you mean
GiteaMirror commented 2025-11-02 06:46:12 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 24, 2020):

I meant exactly what I wrote. If you have a pr head
head and pr base base. The commits displayed are:

git log head...base

What you appear to be asking for instead is something less clever than what git log head...base does probably git log head..base.

If you figure out what the log command of that produces the results that you want we can switch to that

@zeripath commented on GitHub (Oct 24, 2020): I meant exactly what I wrote. If you have a pr head `head` and pr base `base`. The commits displayed are: ``` git log head...base ``` What you appear to be asking for instead is something less clever than what `git log head...base` does probably `git log head..base`. If you figure out what the log command of that produces the results that you want we can switch to that
GiteaMirror commented 2025-11-02 06:46:12 -06:00
Author
Owner
Copy Link

@dschmidt commented on GitHub (Apr 8, 2022):

I just updated to Gitea 1.16.5 from (1.12.x) and now I don't see any new commits in any branch. I.e. it seems to be reproducible 100%.

Is there any news about this?

What I noticed is that I don't see the link to create a new PR on push anymore. Has this feature been removed or is something regarding PRs seriously broken in my setup?

Can I provide anything to help debug this?
I did not see a warning or an error in my logfile and I'm running on log level debug.

@dschmidt commented on GitHub (Apr 8, 2022): I just updated to Gitea 1.16.5 from (1.12.x) and now I don't see any new commits in any branch. I.e. it seems to be reproducible 100%. Is there any news about this? What I noticed is that I don't see the link to create a new PR on push anymore. Has this feature been removed or is something regarding PRs seriously broken in my setup? Can I provide anything to help debug this? I did not see a warning or an error in my logfile and I'm running on log level debug.
GiteaMirror commented 2025-11-02 06:46:12 -06:00
Author
Owner
Copy Link

@nm-bls commented on GitHub (Apr 4, 2023):

This issue still exists.
PR's reliably do not update with new commits on the source branch on my installation (Gitea 1.19).

No errors appear in the logs, however the PR is flagged with the message This pull request is broken due to missing fork information.

@nm-bls commented on GitHub (Apr 4, 2023): This issue still exists. PR's reliably do not update with new commits on the source branch on my installation (Gitea 1.19). No errors appear in the logs, however the PR is flagged with the message ` This pull request is broken due to missing fork information. `
GiteaMirror commented 2025-11-02 06:46:12 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Apr 4, 2023):

See https://docs.gitea.io/en-us/faq/#push-hook--webhook-arent-running.

@delvh commented on GitHub (Apr 4, 2023): See https://docs.gitea.io/en-us/faq/#push-hook--webhook-arent-running.
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#6139
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?