-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Action status check in pr is not updated #23674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
|
@Zettat123 Could you please take a look at it? |
@Yiklek Could you please change on:
pull_request: yes
push:
branches:
- main to on: pull_request and test again? |
@Zettat123 It doesn't work on the pull_request synchronize event yet. The status check is only updated on PR opened. |
|
Maybe my test is incorrect. I'll test again later. |
I can reproduce this in gitea.com and PR's repo is not related https://gitea.com/yp05327/testrepo/pulls/1 |
Fix: #23674 If the type of `hook_event` is `pull_request_sync`, also need to insert a record of `commit_status` into DB. Because `pull_request` event and `pull_request_sync` event have the same payload, so the code is reusable. Screenshot: 
Fix: go-gitea#23674 If the type of `hook_event` is `pull_request_sync`, also need to insert a record of `commit_status` into DB. Because `pull_request` event and `pull_request_sync` event have the same payload, so the code is reusable. Screenshot: 
Backport #23683 by @sillyguodong Fix: #23674 If the type of `hook_event` is `pull_request_sync`, also need to insert a record of `commit_status` into DB. Because `pull_request` event and `pull_request_sync` event have the same payload, so the code is reusable. Screenshot:  Co-authored-by: sillyguodong <33891828+sillyguodong@users.noreply.github.com>
Description
Action status check is not updated on the pull_request synchronize event.
I create a PR
#3
fromdev
tomain
, and the status check is enabled. When I push a commit1703af8060
todev
, action is triggered. But the status check on the PR page is not updated.commit page

action page

Gitea Version
df41181
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?
build Gitea myself
run from command-line
Database
SQLite
The text was updated successfully, but these errors were encountered: