The Vitess 9.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 What does a good PR look like? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 PR Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them, but will have the option to fallback to the old behavior if issues are found. What does a good PR look like? Every GitHub pull request must go through a code review and get approved before it will0 码力 | 417 页 | 2.96 MB | 1 年前3
The Vitess 10.0 Documentation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 What does a good PR look like? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 PR Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them, but will have the option to fallback to the old behavior if issues are found. What does a good PR look like? Every GitHub pull request must go through a code review and get approved before it will0 码力 | 455 页 | 3.07 MB | 1 年前3
The Vitess 11.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 What does a good PR look like? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 PR Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them, but will have the option to fallback to the old behavior if issues are found. What does a good PR look like? Every GitHub pull request must go through a code review and get approved before it will0 码力 | 481 页 | 3.14 MB | 1 年前3
The Vitess 8.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 What does a good PR look like? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them, but will have the option to fallback to the old behavior if issues are found. What does a good PR look like? Every GitHub pull request must go through a code review and get approved before it will where you can discuss the feature and why it’s important. Once that is in place, you can create the PR, as a solution to the problem described in the issue. Separating the need and the solution this way0 码力 | 331 页 | 1.35 MB | 1 年前3
The Vitess 12.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 What does a good PR look like? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 PR Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . but will have the option to fallback to the old behavior if issues are found. 39 What does a good PR look like? Every GitHub pull request must go through a code review and get approved before it will0 码力 | 534 页 | 3.32 MB | 1 年前3
The Vitess 6.0 Documentationshould be zero unresolved discussions when the PR merges. Assigning a Pull Request Vitess uses code owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. GitHub Workflow If you are new to Git and GitHub, we0 码力 | 210 页 | 846.79 KB | 1 年前3
The Vitess 5.0 Documentationshould be zero unresolved discussions when the PR merges. Assigning a Pull Request Vitess uses code owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. GitHub Workflow If you are new to Git and GitHub, we0 码力 | 206 页 | 875.06 KB | 1 年前3
The Vitess 7.0 Documentationshould be zero unresolved discussions when the PR merges. Assigning a Pull Request Vitess uses code owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. 24 GitHub Workflow If you are new to Git and GitHub0 码力 | 254 页 | 949.63 KB | 1 年前3
共 8 条
- 1













