I'm using git bisect to find a failure inducing commit. However, a lot of the commits in the range are definately irrelevant (because they are commits to the documentation or to unit tests). I'd like to make git bisect automatically skip commits which affect files in certain directories. Is this possible somehow?
相关问题
- Why does recursive submodule update from github fa
- Extended message for commit via Visual Studio Code
- Emacs shell: save commit message
- Can I organize Git submodules in a flat hierarchy?
- Upload file > 25 MB on Github
相关文章
- 请教Git如何克隆本地库?
- GitHub:Enterprise post-receive hook
- Git Clone Fails: Server Certificate Verification F
- SSIS solution on GIT?
- Is there a version control system abstraction for
- ssh: Could not resolve hostname git: Name or servi
- Cannot commit changes with gitextensions
- git: retry if http request failed
You have several options here:
Ignoring specific commits
git bisect
contains functionality of skipping commits. You can specify commits, tags, ranges you don't want to test withJust do this before you
git bisect run
, and it should skip what you specified.Specifying folders with broken sources
You can also cut down commits
bisect
tests by specifying what folders it should look for problems in. This is done at the beginning ofbisect
process by supllying additional arguments togit bisect start
(quote from standard manual):Bisect will only consider commits that touch the folders specified.
If you want to automatically gather commits that touch certain files or folders, you may use
git log
for that. For example, the following command will give you commit names that modify files in certain folders:And you can supply the result to
git bisect skip
with use of shell capabilities: