Bug(CI): CI duplication and messiness

[JacobCoffee]

Describe the bug

I'm seeing duplicates in CI after: #2852, specifically in #2868 lint CI runs (runs 2x).

[Check collectstatic / collectstatic (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335873/job/60278606528?pr=2868)Successful in 36s
[CI / migrations (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335870/job/60278606563?pr=2868)
CI / migrations (pull_request)Successful in 1m
[CI / test (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335870/job/60278606515?pr=2868)
CI / test (pull_request)Successful in 4m
Required
[docs/readthedocs.org:pythondotorg](https://pythondotorg--2868.org.readthedocs.build/)
docs/readthedocs.org:pythondotorg — Read the Docs build succeeded!
[Lint / lint (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335874/job/60278606581?pr=2868)
Lint / lint (pull_request)Successful in 16s
[Lint / lint (push)](https://github.com/python/pythondotorg/actions/runs/20972309130/job/60278514578?pr=2868)
Lint / lint (push)Successful in 14s
Terraform Cloud/psf/pythondotorg-infra
Terraform Cloud/psf/pythondotorg-infra

I don't like this and it's confusing to me why we have this problem in the first place because none of my other projects have ever had this weird double CI run thing.

To Reproduce

.

Expected behavior

No duplicates

URL to the issue

No response

Screenshots

Browsers

Other

Operating System

Other

Browser Version

No response

Relevant log output

Additional context

No response

[hugovk]

I'm seeing duplicates in CI after: #2852, specifically in #2868 lint CI runs (runs 2x).

That's because #2852 didn't update lint.yml :)

❯ rg github.event_name
.github/workflows/static.yml
7:    if: github.event_name != 'push' || github.event.repository.fork == true || github.ref == 'refs/heads/main'

.github/workflows/ci.yml
7:    if: github.event_name != 'push' || github.event.repository.fork == true || github.ref == 'refs/heads/main'
43:    if: github.event_name != 'push' || github.event.repository.fork == true || github.ref == 'refs/heads/main'

Adding the condition to lint.yml should fix it.

---

I don't like this and it's confusing to me why we have this problem in the first place because none of my other projects have ever had this weird double CI run thing.

No duplicate builds if pushes are only triggered on main:

on:
  pull_request:
  merge_group:
  push:
    branches:
      - main

https://github.com/litestar-org/litestar/blob/971ee79e3f8a4431c2ace87b8a465a0bc1385f37/.github/workflows/ci.yml#L3-L8

But this prevents contributors from testing feature forks.

(And technically, they're not "duplicate": a push builds what's on the commit on the pushed branch. A pull_request does a simulated merge with the target branch and builds that. Occasionally these produce different results.)