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.

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

Fix activity type match in matchPullRequestEvent (#25746) #25797

Merged
merged 2 commits into from
Jul 10, 2023

Conversation

Zettat123
Copy link
Contributor

Backport #25746

Fix #25736
Caused by #24048

Right now we only check the activity type for pull_request event when types is specified or there are no types and filter. If a workflow only specifies filters but no types like this:

on:
  pull_request:
    branches: [main]

the workflow will be triggered even if the activity type is not one of [opened, reopened, sync]. We need to check the activity type in this case.

Fix go-gitea#25736
Caused by go-gitea#24048

Right now we only check the activity type for `pull_request` event when
`types` is specified or there are no `types` and filter. If a workflow
only specifies filters but no `types` like this:
```
on:
  pull_request:
    branches: [main]
```
the workflow will be triggered even if the activity type is not one of
`[opened, reopened, sync]`. We need to check the activity type in this
case.

Co-authored-by: Giteabot <teabot@gitea.io>
@GiteaBot GiteaBot added this to the 1.19.5 milestone Jul 10, 2023
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Jul 10, 2023
@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 10, 2023
@Zettat123 Zettat123 added type/bug topic/gitea-actions related to the actions of Gitea labels Jul 10, 2023
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Jul 10, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Jul 10, 2023
@lunny lunny added the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Jul 10, 2023
@silverwind silverwind enabled auto-merge (squash) July 10, 2023 12:50
@silverwind silverwind merged commit bd1946e into go-gitea:release/v1.19 Jul 10, 2023
@GiteaBot GiteaBot removed the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Jul 10, 2023
Codeberg-org pushed a commit to Codeberg-org/gitea that referenced this pull request Jul 12, 2023
…o-gitea#25797)

Backport go-gitea#25746

Fix go-gitea#25736
Caused by go-gitea#24048

Right now we only check the activity type for `pull_request` event when
`types` is specified or there are no `types` and filter. If a workflow
only specifies filters but no `types` like this:
```
on:
  pull_request:
    branches: [main]
```
the workflow will be triggered even if the activity type is not one of
`[opened, reopened, sync]`. We need to check the activity type in this
case.

Co-authored-by: Giteabot <teabot@gitea.io>
(cherry picked from commit bd1946e)
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Oct 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. topic/gitea-actions related to the actions of Gitea type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants