You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A future blog post is a blog post with a publication date > current date. Those posts shouldn't appear on the site before their publication date.
Currently, if we have a future blog post merged, it indeed wouldn't appear in the list of blog posts on https://eslint.org/blog/. But it's still rendered, deployed, can be accessed, and appears in the sitemap and in the list of blog posts on its category page (e.g., https://eslint.org/blog/category/case-studies/).
What changes did you make? (Give an overview)
Updated .eleventy.js to completely ignore future blog posts, so they won't be rendered and deployed.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prerequisites checklist
What is the purpose of this pull request?
A future blog post is a blog post with a publication date > current date. Those posts shouldn't appear on the site before their publication date.
Currently, if we have a future blog post merged, it indeed wouldn't appear in the list of blog posts on https://eslint.org/blog/. But it's still rendered, deployed, can be accessed, and appears in the sitemap and in the list of blog posts on its category page (e.g., https://eslint.org/blog/category/case-studies/).
What changes did you make? (Give an overview)
Updated
.eleventy.js
to completely ignore future blog posts, so they won't be rendered and deployed.Related Issues
#645 (comment)
Is there anything you'd like reviewers to focus on?