Lines Matching full:are

18 Often, creating small commits this way results in a number of commits which are
20 push commits which are based on your change still in review. However, when
23 that topics which are not related to each other semantically are also not
24 related to each other in Git until they are merged into master.
37 `git commit --amend`, for which there are many guides online. As mentioned in
44 should be clearly written - even moreso than production code, unit tests are
54 - Concisely, _what_ change are you making? e.g. "docs: convert from US to UK
56 - Comprehensively, _why_ are you making that change? In some cases, like a small
68 Try to include the component you are changing at the front of your subject line;
70 are modifying. e.g. "apphandler: refactor foo to new API"
87 Gerrit; reviewers are not currently added automatically. Maintainers may not see
92 Contributors who are used to code reviews by their team internal to their own
93 company, or who are not used to code reviews at all, are sometimes surprised by
108 The maintainers' job is to ensure that incoming patches are as correct and easy