🐛 Bug: PR Body Workflow makes merging Dependabot updates tedious

[Julian]

Describe the bug

We have https://github.com/json-schema-org/website/blob/main/.github/workflows/pr-body-validation.yml to remind humans to be specific and tidy in their bug reports, but it seems to be set up in a way that also triggers for Dependabot PRs, e.g. #2054

The default dependabot template isn't going to have the fields it seems like we're trying to parse there, but expecting them for a dependabot PR doesn't seem very fruitful to me, so it seems like we should simply be excluding them from consideration.

Steps To Reproduce

See e.g. #2054

Expected Behavior

Dependabot PRs should be mergeable with no additional modification.

Are you working on this issue?

no

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

no

[singhaditya73]

Hey @Julian, I’d like to fix this issue. Could you please assign it to me?

[waygeance]

Hey @Julian , I’d be happy to take this on. Would you mind assigning this issue to me?

[AnujAga2005]

I would like to work on this issue.

[harleenkaur2003]

Hi @Julian ! I can take this up. I’m planning to skip PR body validation for Dependabot PRs by adding a conditional check in the workflow. Let me know if that works.