Annoyingly, no exclude file exists on main yet, and trying to add one here won't work, since the PR base won't have it. So, I am forced to leave a TODO.

And we have the same issue with adding sys.exit(1) to fail the job, it's not on main yet.

I don't like that reusable-*.yml modules are getting more and more jobs. I was hoping to keep them with one job each with any info exchange through inputs/outputs...

I don't like that reusable-*.yml modules are getting more and more jobs. I was hoping to keep them with one job each with any info exchange through inputs/outputs...

In this instance, I think it is better to group them, creating a new module will just introduce more issues with passing inputs IMO.

So we're building docs in the PR, then checking out the base branch, building the docs again, and comparing?

It only takes a couple of minutes for that base branch build, but it feels like we could avoid this extra CI work somehow?

Of course, we don't build docs for every PR, so that reduces it. And we also don't build docs for regular pushes to main, which complicates things.

So we're building docs in the PR, then checking out the base branch, building the docs again, and comparing?

Yeah, that's wasteful.
I was thinking about building and publishing these on docs.python.org. Would that make sense to you?

I was thinking about building and publishing these on docs.python.org. Would that make sense to you?

Then we'd have to host it for every commit, or accept that much more frequent branch updates are necessary (which is also wasteful). For example, commits:

main
- A
- B (Adds an ID)

PR:
- A (base)
# Behind, missing B
- C (Unrelated changes by the PR)

When the CI runs on C, it will pull the base IDs. But, the IDs added by B will be missing at C, so the CI will falsely report it as removed.