Work around spelling exceptions added to release-next

[maelvls]

The problem

Whenever we run mdspell, we first clone every branch (release-1.3, release-1.4, release-next...) into the content/en/docs/ folder.

When words are added to the release-next branch and aren't on master yet, master fails due to the yet-to-be-ignored words are unknown to mdspell.

As an example, the PR #570 added the new spellings "andreas-p" and "renewBefore" to the release-next branch. After the merge, all builds on master started failing since "andreas-p" and "renewBefore" were not present on the master branch's .spelling file.

Idea 1 (this PR)

Ignore spelling of release-next. PRs merged to release-next already have no spelling mistake, so we don't really need to enforce the spelling again.

!content/en/next-docs/**/*.md

Idea 2

Use mdspell's --target-relative which requires copying the .spelling file from the release-next branch and copy it into content/en/next-docs. After looking at verify-lint, one way could be to have a new flag to hugo-multiversion, e.g.,

 ./scripts/bin/multiversion" \
 	--repo-url https://github.com/cert-manager/website.git \
 	--repo-content-dir content/en/docs \
+ 	--repo-content-extra-file .spelling \
 	--output-dir "${REPO_ROOT}/content/en" \
 	--branches v0.13-docs=release-0.13 \
 	--branches v0.12-docs=release-0.12 \
 	--branches next-docs=release-next

Not sure what is the right solution 😅

cc @irbekrm @munnerz

[jetstack-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[irbekrm]

Looks good to me and makes sense- I have added a tiny nit that you can also ignore 😅

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irbekrm, maelvls

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [irbekrm,maelvls]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[irbekrm]

Looks good to me, I've added a small nit, but do unhold if you'd rather merge.

/hold
/lgtm

[irbekrm]

Looks good to me! Thanks for fixing this.

/hold cancel
/lgtm