website-toots/108236350943922525.md

id	in_reply_to_id	in_reply_to_account_id	sensitive	spoiler_text	visibility	language	replies_count	reblogs_count	favourites_count	edited_at	reblog	application	account	media_attachments	mentions	tags	emojis	card	poll	syndication	date
108236350943922525	null	null	false		public	en	1	3	4	null	null	null	id username acct display_name url uri avatar avatar_static header header_static noindex roles 108219415927856966 brozek brozek Brandon Rozek https://fosstodon.org/@brozek https://fosstodon.org/users/brozek https://cdn.fosstodon.org/accounts/avatars/108/219/415/927/856/966/original/bae9f46f23936e79.jpg https://cdn.fosstodon.org/accounts/avatars/108/219/415/927/856/966/original/bae9f46f23936e79.jpg https://fosstodon.org/headers/original/missing.png https://fosstodon.org/headers/original/missing.png true			name url git https://fosstodon.org/tags/git		url title description language type author_name author_url provider_name provider_url html width height image image_description embed_url blurhash published_at https://brandonrozek.com/blog/git-bisect-broken-builds/ Which commit broke the build? Using Git Bisect Lets imagine a scenario where in the latest merge a test starts failing. Lets say these tests are saved in test.sh. Instead of having to test each individual commit in the merge, to see where the test fails, luckily git bisect narrows it down in a more efficient way! To use: git bisect start [good] [bad] git bisect run test.sh Where [good] and [bad] are replaced with their respective commit hashes. null link Brandon Rozek https://brandonrozek.com/ 0 0 null null null	null	https://fosstodon.org/@brozek/108236350943922525	2022-05-03T05:27:27.957Z

{{< unsafe >}}

Wrote a blog post on using `git bisect` to efficiently find where a test script fails.

https://brandonrozek.com/blog/git-bisect-broken-builds/

I don't know how I used #git for so long before learning about this 😲

{{< /unsafe >}}