Compare commits

...

2 Commits

Author SHA1 Message Date
LFC
6593996255 Update project name from DataFusion to GreptimeDB 2025-12-24 16:14:39 +08:00
LFC
4a1156ba0b Fix typo in AI-assisted contributions policy 2025-12-24 16:11:03 +08:00

View File

@@ -104,14 +104,14 @@ All commit messages SHOULD adhere to the [Conventional Commits specification](ht
## AI-Assisted contributions
We has the following policy for AI-assisted PRs:
We have the following policy for AI-assisted PRs:
- The PR author should **understand the core ideas** behind the implementation **end-to-end**, and be able to justify the design and code during review.
- **Calls out unknowns and assumptions**. It's okay to not fully understand some bits of AI generated code. You should comment on these cases and point them out to reviewers so that they can use their knowledge of the codebase to clear up any concerns. For example, you might comment "calling this function here seems to work but I'm not familiar with how it works internally, I wonder if there's a race condition if it is called concurrently".
### Why fully AI-generated PRs without understanding are not helpful
Today, AI tools cannot reliably make complex changes to DataFusion on their own, which is why we rely on pull requests and code review.
Today, AI tools cannot reliably make complex changes to GreptimeDB on their own, which is why we rely on pull requests and code review.
The purposes of code review are: