Avoid reporting errors when making PRs across forks

[adam-vessey]

Purpose / why

Has come up a number of times, of documentation PRs reporting errors due to PRs being made from a fork, so, let's avoid the errors.

See: rossjrw/pr-preview-action#6

What changes were made?

Only generates the preview if the PR is made from the same fork.

Verification

Interested Parties

• @Islandora/documentation
• @Islandora/committers

Checklist

Pull-request Reviewer

Pull-request reviewer should ensure the following:

• Does this PR link to related issues?
• Does the proposed documentation align with the Islandora Documentation Style Guide?
• Are the changes accurate, useful, free of typos, etc?

Person Merging

The person merging should ensure the following:

• Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
• If pages are renamed or removed, have all internal links to those pages been fixed?
• If pages are added, have they been linked to or placed in the menu?
• Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

[github-actions]

PR Preview Action v1.4.4
Preview removed because the pull request was closed.
2023-09-13 21:38 UTC