File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -104,9 +104,9 @@ the following strategies:
104
104
* Use ` $git blame ` to see where changes were introduced. Look at the commit
105
105
message, check changes that were made to the code in the same commit. If you
106
106
are using the GUI of GitHub, you can easily obtain more contextual information
107
- such as the pull request with which a change was introdued . Often
108
- functionality was introduced with testing. So you can easily see which new
109
- tests are related to the new functionality. You can remvoe the changes in the
107
+ such as the pull request with which a change was introduced . Often
108
+ functionality was introduced with testing. So, you can easily see which new
109
+ tests are related to the new functionality. You can remove the changes in the
110
110
source code and re-run the tests and see what fails and why.
111
111
* Search Issues and Pull Requests on GitHub with the full text search. Make
112
112
sure you also search for closed Issues and PRs.
You can’t perform that action at this time.
0 commit comments