Skip to content
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

chore(recipes): Add codeowners to gatsby-recipes #23146

Merged
merged 1 commit into from
Apr 15, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CODEOWNERS
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,5 @@
/themes/ @gatsbyjs/themes-core
/packages/gatsby-plugin-mdx/ @gatsbyjs/themes-core
/packages/gatsby/src/bootstrap/load-themes @gatsbyjs/themes-core
/packages/gatsby-recipes/ @gatsbyjs/themes-core
/packages/gatsby/src/internal-plugins/webpack-theme-component-shadowing/ @gatsbyjs/themes-core
3 changes: 2 additions & 1 deletion packages/gatsby-recipes/src/todo.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,11 +54,12 @@ John
- [x] spike on bundling recipes into one file
- [x] print pretty error when there's parsing errors of mdx files
- [x] Move mdx recipes to its own package `gatsby-recipes` & pull them from unpkg
- [ ] add CODEOWNERS file for recipes
- [x] add CODEOWNERS file for recipes
- [ ] give proper npm permissions to `gatsby-recipes`
- [x] validate that the first step of recipes don't have any resources. They should just be for the title/description
- [x] handle not finding a recipe
- [x] test modifying gatsby-config.js from default starter
- [ ] getting tests passing

## Near-ish future

Expand Down