Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create commit status when event is pull_request_sync (#23683) #23691

Merged
merged 3 commits into from
Mar 24, 2023
Merged

Create commit status when event is pull_request_sync (#23683) #23691

merged 3 commits into from
Mar 24, 2023

Commits on Mar 24, 2023

  1. Create commit status when event is pull_request_sync (go-gitea#23683) 

    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:

![image](https://user-images.githubusercontent.com/33891828/227465436-1b436807-d0b2-4a2b-8890-09d96c7f666d.png)
    @sillyguodong @GiteaBot
    sillyguodong authored and GiteaBot committed Mar 24, 2023
    Configuration menu
    Copy the full SHA
    23a94e1 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'release/v1.19' into backport-23683-v1.19

    @techknowlogick
    techknowlogick authored Mar 24, 2023
    Configuration menu
    Copy the full SHA
    b69aaa6 View commit details
    Browse the repository at this point in the history

  3. Merge branch 'release/v1.19' into backport-23683-v1.19

    @jolheiser
    jolheiser authored Mar 24, 2023
    Configuration menu
    Copy the full SHA
    0b7dc29 View commit details
    Browse the repository at this point in the history