ci: allow pushes to main to deploy

[agoose77]

I noticed that #1836 didn't trigger an RTD build for pushes to main, so I've updated docs.yml

I find the expression NOT (X AND NOT Y) clearer than (NOT X) OR Y because in this case X and Y are related. We only avoid deploying the docs if the event was a PR event, and the PR does not originate from scikit-hep/awkward

---

📚 The documentation for this PR will be available at https://awkward-array.readthedocs.io/en/agoose77-ci-docs-deploy-on-main/ once Read the Docs has finished building 🔨

[codecov]

Codecov Report

Merging #1852 (bd60862) into main (31ecdf2) will decrease coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files

Impacted Files	Coverage Δ
src/awkward/contents/indexedarray.py	76.60% <0.00%> (-0.19%)	⬇️
src/awkward/contents/recordarray.py	83.87% <0.00%> (-0.19%)	⬇️
src/awkward/_util.py	82.21% <0.00%> (-0.18%)	⬇️
src/awkward/contents/indexedoptionarray.py	88.90% <0.00%> (-0.16%)	⬇️
src/awkward/_connect/avro.py	87.17% <0.00%> (-0.14%)	⬇️
src/awkward/types/_awkward_datashape_parser.py	47.72% <0.00%> (-0.01%)	⬇️

[agoose77]

It's not easy to guarantee that this is working, but if the docs deploy for this PR then we'll know at least that it didn't break anything :)

[jpivarski]

I frequently get boolean logic backward, too. But the good thing is that it's easy to notice with a test, since it will either always work or always fail.

I verified that the docs for this branch got pushed, so I guess it worked!

[agoose77]

For posterity - the docs were deploying on the branch. The problem was that I made an oversight and didn't think about the case where the docs workflow runs on push (not pull_request) to main. In that case, the github.event.pull_request object is null, so the condition always fails. So, let's now see if this merged PR deploys...