Skip to content

[bug] needs to fix CI for strange duplicated checks in PR #14

@nomeguy

Description

@nomeguy

The following duplicated CI checks ran in this open PR: #13

[Build / Running Go tests (pull_request)](https://github.com/casbin/zap-logger/actions/runs/21559242983/job/62120636290?pr=13)
Build / Running Go tests (pull_request)Successful in 39s
[Build / Running Go tests (push)](https://github.com/casbin/zap-logger/actions/runs/21559242543/job/62120636229?pr=13)
Build / Running Go tests (push)Successful in 37s
[CI / semantic-release (pull_request)](https://github.com/casbin/zap-logger/actions/runs/21559242970/job/62120651038?pr=13)
CI / semantic-release (pull_request)Successful in 3s
[CI / semantic-release (push)](https://github.com/casbin/zap-logger/actions/runs/21559242538/job/62120649604?pr=13)
CI / semantic-release (push)Successful in 21s
[CI / test (pull_request)](https://github.com/casbin/zap-logger/actions/runs/21559242970/job/62120636195?pr=13)
CI / test (pull_request)Successful in 24s
[CI / test (push)](https://github.com/casbin/zap-logger/actions/runs/21559242538/job/62120636183?pr=13)
CI / test (push)Successful in 21s

I think for an open state PR, it should not run "XXX (push)" checks, right? It should run for the git push after PR merge?
Need to fix the CI.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions