We will ask that you sign a Contributor License Agreement before we accept any contributions into our repo.

Please keep PRs small and selfcontained. This allows code reviewers (see below) to focus and fully understand the PR. A good rule of thumb is less than 1000 lines changed. (One exception is a mechanistic refactor, like renaming, that is conceptually trivial but might have a large line count.)

Please keep PRs small and self-contained. This allows code reviewers (see below) to focus and fully understand the PR. A good rule of thumb is less than 1000 lines changed. (One exception is a mechanistic refactor, like renaming, that is conceptually trivial but might have a large line count.)

If your intended feature or refactor will be larger than this:

Each PR:

- Must individually build and pass all tests, including formatting and linting.

- Must not introduce regressions orbackcompatibility issues, evenif alater PR would resolve the issue.

- Must not introduce regressions orbackward-compatibility issues, evenif asubsequent PRin your series would resolve the issue.

- Should be a conceptually coherent change set.

In practice, many of these smaller PRs will be invisible to end users, and that is ok. For example, you might introduce