PR's status doesn't update automatically when I do a branch merge locally #11568

Closed
opened 2025-11-02 09:41:17 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @CaiCandong on GitHub (Aug 31, 2023).

Description

Reproduction:

  1. Initialize a repository locally and open two branches, main and pr
git init
git checkout -b main
touch README.md
git add README.md
git commit -m "first commit"
git remote add origin http://host/user/repo.git
echo abc >> readme.md && git commit -am "abc"
git checkout -b pr
echo efg >> readme.md && git commit -am "efg"
  1. Push both main and pr to gitea.
git push origin --all
  1. Create a PR on gitea
    image

  2. Finish branch merge push to remote repository locally

git switch main 
git merge pr
git push origin main 
  1. Result
    image

Gitea Version

try.gitea.io

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

try.gitea.io

Database

None

Originally created by @CaiCandong on GitHub (Aug 31, 2023). ### Description Reproduction: 1. Initialize a repository locally and open two branches, `main` and `pr` ``` git init git checkout -b main touch README.md git add README.md git commit -m "first commit" git remote add origin http://host/user/repo.git echo abc >> readme.md && git commit -am "abc" git checkout -b pr echo efg >> readme.md && git commit -am "efg" ``` 2. Push both `main` and `pr` to gitea. ``` git push origin --all ``` 3. Create a PR on gitea ![image](https://github.com/go-gitea/gitea/assets/50507092/5e32c315-8a6a-4876-8bef-2274a9e01fa5) 4. Finish branch merge push to remote repository locally ``` git switch main git merge pr git push origin main ``` 5. Result ![image](https://github.com/go-gitea/gitea/assets/50507092/8b0bc84d-2add-4fc5-8fcd-7b05e1894925) ### Gitea Version try.gitea.io ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? try.gitea.io ### Database None
GiteaMirror added the type/bug label 2025-11-02 09:41:17 -06:00
Author
Owner

@CaiCandong commented on GitHub (Aug 31, 2023):

I found that the error had to do with this option, which is off by default, but when I made the error, gitea didn't give me any indication to turn it on, which is very impersonal.

image

@CaiCandong commented on GitHub (Aug 31, 2023): I found that the error had to do with this option, which is off by default, but when I made the error, gitea didn't give me any indication to turn it on, which is very impersonal. ![image](https://github.com/go-gitea/gitea/assets/50507092/6248d4c0-5a55-4fa0-b327-1dd11efb4fc6)
Author
Owner

@yp05327 commented on GitHub (Mar 21, 2024):

I found that the error had to do with this option, which is off by default, but when I made the error, gitea didn't give me any indication to turn it on, which is very impersonal.

So this is not a bug? As we have this option.

@yp05327 commented on GitHub (Mar 21, 2024): > I found that the error had to do with this option, which is off by default, but when I made the error, gitea didn't give me any indication to turn it on, which is very impersonal. So this is not a bug? As we have this option.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11568