Lint for Hugo aliases with absolute paths

[sftim]

This is a Feature Request

What would you like to be added

Create a new lint, applied to new pull requests, that checks for front matter that adds a Hugo alias with a leading /.

For example, reject this:

---
title: Some Kubernetes page
weight: 10
aliases: [/some-page/,/some-other-thing/]
---

Why is this needed
Based on experience from the fix in PR #18895 and some other stuff I wasn't involved in, it seems like this site never has a use for Hugo aliases that have a leading /.
If that's the case, how about linting for that? It can be a local check and also happen in CI.

Comments
/kind feature
/priority backlog

[Colstuwjx]

How about adding this lint inside makefile and ensure it happens before executing netlify site build ?

[sftim]

@Colstuwjx if you have the appetite for a pull request to add this, I'm all for it.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[sftim]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.