Lines Matching refs:t

6 Docker is handy because it's fairly portable, and won't interfere with the rest
43 Your new worktree doesn't know about any untracked files you have in your main
46 `run-unit-test-docker.sh`, you can't run the CI with untracked changes anyways,
47 so this isn't the worst thing in the world. (If you make untracked changes in
61 convenience, since you can't check out a branch in your worktree that's already
64 However, Git won't be able to figure out how to get to your main worktree
115 This is especially not recommended, since you won't be able to work on your code
129 The first run will take a long time! But afterwards it shouldn't be so bad, as
261 `get_record_id()` will be identical, so we won't cover them here.
266 sure that the MSB and LSB values are different (don't use `0x3333` as the
288 We don't expect that our `GetSdrReq` pointer will ever be null; in this case,
290 specify that in the unlikely case we're given a null pointer, we die. We don't
374 this with interactive rebase, which won't be described here.)
400 Don't test other people's code. Make sure to limit the test assertions to the
401 code under test. For example, don't test what happens if you give a bad input to
404 However, don't trust other people's code, either! Try to test _how you respond_
414 for code that wasn't previously unit-tested. It's okay to check in a bugfix
442 about and it isn't covered, you should mention it to the committer.
458 This won't disturb the rest of your Git repo state, and will put your CI
465 - Jenkins isn't responding
467 - The committer doesn't have "Ok-To-Test" permission, and you don't have