Skip to content

Feat/future deploy warning#232

Open
SamBarker wants to merge 5 commits intokroxylicious:mainfrom
SamBarker:feat/future-deploy-warning
Open

Feat/future deploy warning#232
SamBarker wants to merge 5 commits intokroxylicious:mainfrom
SamBarker:feat/future-deploy-warning

Conversation

@SamBarker
Copy link
Member

@SamBarker SamBarker commented Mar 4, 2026

This PR adds a couple of checks.

  1. To catch PRs where the front matter is older than the filename. likely to be a mistake.
  2. To add a warning on merge when future dated posts are merged as they require manual publishing. Example https://github.com/SamBarker/kroxylicious.github.io/actions/runs/22653880628

When a push to main includes future-dated posts, the deploy workflow
now adds a warning to the GitHub Actions job summary listing the
affected posts and their publish dates, with a reminder to re-run
the workflow manually on the publish date.

Both the filename date and front matter date are checked, using
whichever is later.

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Sam Barker <sam@quadrocket.co.uk>
Adds a PR check that fails if any post in _posts/ has a filename date
that doesn't match the date in its front matter, catching accidental
mismatches early.

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Sam Barker <sam@quadrocket.co.uk>
@robobario
Copy link
Member

oof. so if we deploy in advance they don't get built into the static output?

Rather than requiring an exact match, only fail if the front matter
date is older than the filename date, which is the case that would
cause Jekyll to publish later than expected.

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Sam Barker <sam@quadrocket.co.uk>
@SamBarker SamBarker marked this pull request as ready for review March 4, 2026 03:36
@SamBarker SamBarker requested a review from a team as a code owner March 4, 2026 03:36
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