blob: 6aed80671359d17254c6d4dca3f8e6fbb84ed1f2 (
about) (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
#
msgid ""
msgstr ""
msgid "title: Git bisect automation"
msgstr ""
msgid "layout: post"
msgstr ""
msgid "lang: en"
msgstr ""
msgid "ref: git-bisect-automation"
msgstr ""
msgid ""
"It is good to have an standardized way to run builds and tests on the "
"repository of a project, so that you can find when a bug was introduced by "
"using `git bisect run`."
msgstr ""
msgid ""
"I've already been in the situation when a bug was introduced and I didn't "
"know how it even was occurring, and running Git bisect over hundreds of "
"commits to pinpoint the failing commit was very empowering:"
msgstr ""
msgid ""
"$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46\n"
"$ git bisect start HEAD $GOOD_COMMIT_SHA\n"
"$ git bisect run sn -c './build.sh && ./run-failing-case.sh'\n"
msgstr ""
msgid ""
"Git will than do a binary search between the commits, and run the commands "
"you provide it with to find the failing commit."
msgstr ""
msgid ""
"Instead of being afraid of doing a bisect, you should instead leverage it, "
"and make Git help you dig through the history of the repository to find the "
"bad code."
msgstr ""
msgid "date: 2020-11-12 2"
msgstr ""
#~ msgid "date: 2020-11-12"
#~ msgstr ""
|
