-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add turbopack team to CODEOWNERS #2420
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Ignored Deployments
|
/Cargo.lock | ||
/Cargo.toml | ||
/rust-toolchain | ||
/pnpm-lock.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we just leave that as nothing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey just saw this comment! What do you mean leave that as nothing? As in, nobody owns it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, the lock file could be changed because of something in the docs
or something in the crates
folder, so I feel like it alone shouldn't assign anyone 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha. (1) I didn't realize that leaving it empty would assign no one (that's cool if true!), but (2) the way it's structured now is that all files are co-owned by both teams unless specified otherwise. If we left it blank and no-one is assigned, would the PR author pick people to ✅ manually? I think we'd still need approvers, right?
No description provided.