1
00:00:01,090 --> 00:00:02,370
[Autogenerated] So in this module we're

2
00:00:02,370 --> 00:00:04,140
going to be using git and one of the tools

3
00:00:04,140 --> 00:00:07,020
provided by get to help find bugs within

4
00:00:07,020 --> 00:00:09,570
our repositories. But first, let's quickly

5
00:00:09,570 --> 00:00:11,090
review Global Man Ticks, the fictional

6
00:00:11,090 --> 00:00:12,380
company that we have been following

7
00:00:12,380 --> 00:00:14,240
throughout this course they were first

8
00:00:14,240 --> 00:00:16,550
looking to configure. Newgate installs an

9
00:00:16,550 --> 00:00:19,210
able code reuse, developed a local

10
00:00:19,210 --> 00:00:21,440
workflow for running tests and Linton Per

11
00:00:21,440 --> 00:00:23,710
commit and enforcing a commit message

12
00:00:23,710 --> 00:00:25,660
template on the server. And currently

13
00:00:25,660 --> 00:00:27,170
through the previous modules, we have been

14
00:00:27,170 --> 00:00:29,650
able to meet all of those needs. Next,

15
00:00:29,650 --> 00:00:31,100
we're going to talk about enabling

16
00:00:31,100 --> 00:00:33,910
developers to work more efficiently and

17
00:00:33,910 --> 00:00:35,750
one of the key aspects of any development.

18
00:00:35,750 --> 00:00:38,500
Workflow is finding bugs, and so we're

19
00:00:38,500 --> 00:00:40,310
going to see the tools that get provides

20
00:00:40,310 --> 00:00:42,880
to help us with that process. So first of

21
00:00:42,880 --> 00:00:45,300
all, in this module, we will be reviewing

22
00:00:45,300 --> 00:00:48,440
to get bisect tool and its capabilities

23
00:00:48,440 --> 00:00:50,820
then will be utilizing. Get bisect to

24
00:00:50,820 --> 00:00:52,980
manually determine when bad code was

25
00:00:52,980 --> 00:00:55,640
injected within our repositories, and then

26
00:00:55,640 --> 00:00:58,060
ultimately we will be utilizing get bisect

27
00:00:58,060 --> 00:01:03,000
toe, automatically determine when bad code was injected

