Skip to content

Forbid migration alias in new posts #1629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 30, 2025
Merged

Forbid migration alias in new posts #1629

merged 1 commit into from
May 30, 2025

Conversation

senekor
Copy link
Contributor

@senekor senekor commented May 30, 2025

The change is explained in a comment, copying it here for convenience:

Make sure that posts created after the migration to Zola don't have
the alias for preserving permalinks.

Blog authors would often copy-paste an old post, reusing the
boilerplate for a new one. In that process, they'd usually preserve
that alias as well, probably not knowing what it's for. Technically
such an alias doesn't hurt much, it's just a redirect that isn't
referenced anywhere. So these aliases were allowed, preferring not to
bother blog authors with such unimportant stuff.

However, there was a situation where a blog post was merged with
the wrong publication date because of this. Shortly before merging,
the date was updated, but it was accidentally changed in the useless
alias instead of the authoritative path key. Because of this
footgun, we don't allow creating these new aliases anymore.

Blog authors who copy-paste old boilerplate will run into failed CI
and have to fix it by removing the alias. It's annoying, but better
than publishing a post with the wrong publication date.

Rendered

@senekor
Copy link
Contributor Author

senekor commented May 30, 2025

I was also once asked about the aliases key, so it seems to be causing confusion even when things do go well.

@senekor senekor requested a review from Manishearth May 30, 2025 15:51
@senekor senekor merged commit bca2dad into master May 30, 2025
5 checks passed
@senekor senekor deleted the senekor-lwyvtxwxukqx branch May 30, 2025 16:32
@senekor senekor mentioned this pull request Jun 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants