-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat: Schedule blog post #645
Conversation
✅ Deploy Preview for new-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for es-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for ja-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for hi-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for zh-hans-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for fr-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for pt-br-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for de-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Post looks good to me! One thing I noticed is that even though I have an author bio defined in the repo (from my previous post) I don't see it used anywhere in this post. Is that expected? |
I tested this locally with
Maybe we should fix this before merging? PR: #646 |
Author bio is at the end of the blog post: |
Now that #646 is merged, I think it should be safe to merge this? We do a nightly data fetch to regenerate the site, so I think this will get automatically published on Tuesday. |
Yes, I'll merge it now and check the build log and the site.
It should be as there's always some change in the data. I'll doublecheck on Tuesday. |
Works fine:
And https://eslint.org/blog/2024/10/code-review-nit-to-ecosystem-improvements/ doesn't exist yet. |
The blog post is published now: https://eslint.org/blog/2024/10/code-review-nit-to-ecosystem-improvements/ |
Prerequisites checklist
What is the purpose of this pull request?
Schedule @captbaritone's blog post for next Tuesday.
Is there anything you'd like reviewers to focus on?
It should be safe to merge this ahead of time because we don't render future posts in production.