BAETYL 0.1.6 Documentation23 BAETYL Documentation 3.2 Code Review • About Golang format, please refer to Go Code Review Comments. • Please feel free to ping your reviewers by sending them the URL of your pull request via email If you don’t want your reviewers to get overwhelmed by email notifications, you might reply their comments by in a batch. • Reduce the unnecessary commits. Some developers commit often. It is recommended0 码力 | 120 页 | 7.27 MB | 1 年前3
BAETYL 0.1.6 Documentationthe Baetyl official repository. Code Review About Golang format, please refer to Go Code Review Comments [https://github.com/golang/go/wiki/CodeReviewComments]. Please feel free to ping your reviewers If you don’t want your reviewers to get overwhelmed by email notifications, you might reply their comments by in a batch [https://help.github.com/articles/reviewing- proposed-changes-in-a-pull-request/]0 码力 | 119 页 | 11.46 MB | 1 年前3- BAETYL 1.0.0 Documentationthe Baetyl official repository. Code Review About Golang format, please refer to Go Code Review Comments [https://github.com/golang/go/wiki/CodeReviewComments]. Please feel free to ping your reviewers If you don’t want your reviewers to get overwhelmed by email notifications, you might reply their comments by in a batch [https://help.github.com/articles/reviewing- proposed-changes-in-a-pull-request/]0 码力 | 135 页 | 15.44 MB | 1 年前3
- BAETYL 1.0.0 Documentation23 BAETYL Documentation 3.2 Code Review • About Golang format, please refer to Go Code Review Comments. • Please feel free to ping your reviewers by sending them the URL of your pull request via email If you don’t want your reviewers to get overwhelmed by email notifications, you might reply their comments by in a batch. • Reduce the unnecessary commits. Some developers commit often. It is recommended0 码力 | 145 页 | 9.31 MB | 1 年前3
共 4 条
- 1