New/Modified Toots

This commit is contained in:
GitHub Actions Bot 2024-10-08 23:26:33 +00:00
parent d5677ed188
commit 752403f3d3
89 changed files with 89 additions and 89 deletions

View file

@ -1 +1 @@
{"account":{"acct":"brozek","avatar":"https://cdn.fosstodon.org/accounts/avatars/108/219/415/927/856/966/original/bae9f46f23936e79.jpg","display_name":"Brandon Rozek","header":"https://fosstodon.org/headers/original/missing.png","id":"108219415927856966","uri":"https://fosstodon.org/users/brozek","url":"https://fosstodon.org/@brozek","username":"brozek"},"application":null,"card":{"author_name":"Brandon Rozek","author_url":"https://brandonrozek.com/","blurhash":null,"description":"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!\nTo use:\ngit bisect start [good] [bad] git bisect run test.sh Where [good] and [bad] are replaced with their respective commit hashes.","embed_url":"","height":0,"html":"","image":null,"image_description":"","language":null,"provider_name":"","provider_url":"","published_at":null,"title":"Which commit broke the build? Using Git Bisect","type":"link","url":"https://brandonrozek.com/blog/git-bisect-broken-builds/","width":0},"content":"<p>Wrote a blog post on using `git bisect` to efficiently find where a test script fails.</p><p><a href=\"https://brandonrozek.com/blog/git-bisect-broken-builds/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">brandonrozek.com/blog/git-bise</span><span class=\"invisible\">ct-broken-builds/</span></a></p><p>I don&#39;t know how I used <a href=\"https://fosstodon.org/tags/git\" class=\"mention hashtag\" rel=\"tag\">#<span>git</span></a> for so long before learning about this 😲</p>","date":"2022-05-03T05:27:27.957Z","edited_at":null,"emojis":[],"favourites_count":4,"id":"108236350943922525","in_reply_to_account_id":null,"in_reply_to_id":null,"language":"en","media_attachments":[],"mentions":[],"poll":null,"reblog":null,"reblogs_count":3,"replies_count":1,"sensitive":false,"spoiler_text":"","syndication":"https://fosstodon.org/@brozek/108236350943922525","tags":[{"name":"git","url":"https://fosstodon.org/tags/git"}],"visibility":"public"}
{"account":{"acct":"brozek","avatar":"https://cdn.fosstodon.org/accounts/avatars/108/219/415/927/856/966/original/bae9f46f23936e79.jpg","display_name":"Brandon Rozek","header":"https://fosstodon.org/headers/original/missing.png","hide_collections":false,"id":"108219415927856966","indexable":false,"uri":"https://fosstodon.org/users/brozek","url":"https://fosstodon.org/@brozek","username":"brozek"},"application":null,"card":{"author_name":"Brandon Rozek","author_url":"https://brandonrozek.com/","authors":[{"account":null,"name":"Brandon Rozek","url":"https://brandonrozek.com/"}],"blurhash":null,"description":"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!\nTo use:\ngit bisect start [good] [bad] git bisect run test.sh Where [good] and [bad] are replaced with their respective commit hashes.","embed_url":"","height":0,"html":"","image":null,"image_description":"","language":null,"provider_name":"","provider_url":"","published_at":null,"title":"Which commit broke the build? Using Git Bisect","type":"link","url":"https://brandonrozek.com/blog/git-bisect-broken-builds/","width":0},"content":"<p>Wrote a blog post on using `git bisect` to efficiently find where a test script fails.</p><p><a href=\"https://brandonrozek.com/blog/git-bisect-broken-builds/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">brandonrozek.com/blog/git-bise</span><span class=\"invisible\">ct-broken-builds/</span></a></p><p>I don&#39;t know how I used <a href=\"https://fosstodon.org/tags/git\" class=\"mention hashtag\" rel=\"tag\">#<span>git</span></a> for so long before learning about this 😲</p>","date":"2022-05-03T05:27:27.957Z","edited_at":null,"emojis":[],"favourites_count":4,"id":"108236350943922525","in_reply_to_account_id":null,"in_reply_to_id":null,"language":"en","media_attachments":[],"mentions":[],"poll":null,"reblog":null,"reblogs_count":3,"replies_count":1,"sensitive":false,"spoiler_text":"","syndication":"https://fosstodon.org/@brozek/108236350943922525","tags":[{"name":"git","url":"https://fosstodon.org/tags/git"}],"visibility":"public"}