这是indexloc提供的服务,不要输入任何密码
Skip to content

feat(docs): 1.7 blog post #3264

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 8 commits into from
Jan 12, 2023
Merged

Conversation

tknickman
Copy link
Member

Blog post for turbo@1.7

@tknickman tknickman requested review from a team as code owners January 11, 2023 16:01
@vercel
Copy link

vercel bot commented Jan 11, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
examples-cra-web 🔄 Building (Inspect) Jan 12, 2023 at 3:55AM (UTC)
examples-kitchensink-blog 🔄 Building (Inspect) Jan 12, 2023 at 3:55AM (UTC)
examples-tailwind-web 🔄 Building (Inspect) Jan 12, 2023 at 3:55AM (UTC)
7 Ignored Deployments
Name Status Preview Comments Updated
examples-basic-web ⬜️ Ignored (Inspect) Visit Preview Jan 12, 2023 at 3:55AM (UTC)
examples-designsystem-docs ⬜️ Ignored (Inspect) Jan 12, 2023 at 3:55AM (UTC)
examples-native-web ⬜️ Ignored (Inspect) Jan 12, 2023 at 3:55AM (UTC)
examples-nonmonorepo ⬜️ Ignored (Inspect) Jan 12, 2023 at 3:55AM (UTC)
examples-svelte-web ⬜️ Ignored (Inspect) Jan 12, 2023 at 3:55AM (UTC)
turbo-site ⬜️ Ignored (Inspect) Visit Preview Jan 12, 2023 at 3:55AM (UTC)
turbo-vite-web ⬜️ Ignored (Inspect) Jan 12, 2023 at 3:55AM (UTC)

@github-actions
Copy link
Contributor

github-actions bot commented Jan 11, 2023

🟢 CI successful 🟢

Thanks

'jaredpalmer',
'mehulkar',
'chrisolszewski',
'nicholasyang'
Copy link
Contributor

@mehulkar mehulkar Jan 12, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious... are we just copy pasting everyone onto every post? seems like it would be nicer / more meaningful if we filtered this list by whoever's actually writing (and acknowledge code contributions in the post itself if we want to do that)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whole team is typically involved with the release blog posts in some aspect (from writing to reviewing to publishing) - so it's simpler in my opinion to list the core team as the authors. Plus we're all hashing out all the content day to day as a team anyway. We're a team and we're all involved here.

For the more specific one offs (like https://turbo.build/blog/turbopack-benchmarks) I think those make sense to list writing authors only.

I could be convinced otherwise as well, but I don't really feel the need to be pedantic about the bar for entry to a release post.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, just gut checking :).

We're a team and we're all involved here.

💯 💟

@kodiakhq kodiakhq bot merged commit b479f0a into main Jan 12, 2023
@kodiakhq kodiakhq bot deleted the tomknickman/turbo-532-turborepo-17-blogpost branch January 12, 2023 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Improvements or additions to documentation area: site pr: automerge Kodiak will merge these automatically after checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants