feat(release): auto-generate blog posts#213
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
avivkeller
changed the title
avivkeller
changed the title
⚡ Lighthouse reportAudited the Vercel preview deployment: https://webpack-doc-bd6jcoy0z-openjs.vercel.app
|
| const getRemovedChangesets = async version => { | ||
| const { files = [] } = await fetchJSON(`${API_BASE}/commits/${version}`); | ||
|
|
||
| return files.filter( | ||
| file => | ||
| file.status === 'removed' && | ||
| file.filename.startsWith('.changeset/') && | ||
| file.patch | ||
| ); | ||
| }; |
There was a problem hiding this comment.
Hmm, I'd rather open it about a week before the release, or whenever Alex says we're getting close, so we have time to make any necessary changes
There was a problem hiding this comment.
I can do that, but the idea behind automating is that you need to make minimal changes to the document
There was a problem hiding this comment.
yep, although I guess I could get used to writing the blog post after the release and making any necessary changes afterward
There was a problem hiding this comment.
Well, if it's easier to run before, I'm happy to make that change, you are the author, just keep in mind I don't think there's a way for us to automate "1 week before" without a manual trigger.
I can do:
- On manual trigger w/ version, check the tag for changesets, fall back to
main - If no blog post created before
releasetriggered, run automatically?
There was a problem hiding this comment.
On manual trigger w/ version, check the tag for changesets, fall back to main
If no blog post created before release triggered, run automatically?
Yeah, I think that would be the right workflow.
cc @bjohansebas