This mode overlays the new image over the old one, and lets you control the transparency. This is an excellent way of noticing small changes within an image, whilst still keeping track of the overall image. This mode displays the two versions of the image with a left to right slider over the top. Unfortunately, this mode does not help when identifying small visual changes within the image itself, the other modes are better for that. This is a great way to notice an image has slightly changed dimensions, since this might not be noticeable with the naked eye. This mode displays the images side by side, as well as their width, height, and file size. For the compatible file types, there are 3 options for the rich diff: 2-up I found SVGs, PNGs, JPGs, and GIFs can use rich diff, but BMPs cannot. I created a collection of test images (SVG, PNG, JPG, GIF, BMP), committed them, and then committed new versions of each. Images are probably the best use cases for rich diff. If no “page” icon is visible, rich diff is not available. Overallįirst of all, how do you access rich diff? Simple, click the “page” icon next to many file types! Once clicked, this will compare the two files in a much more helpful way. I’ll briefly run through the functionality it offers, all screenshots in this post are from my Rich Diff repo. ![]() Luckily, I recently discovered the rarely mentioned “rich diff” feature that makes this so, so much easier. However, comparing images can be much harder to check, since by default GitHub only shows an unintuitive “Binary file not shown” message. When reviewing pull requests, code changes are very easy to review and approve. ![]() In fact, according to GitHub that’s around 20% of my day! Like many developers, I spend a surprisingly large amount of time reviewing other people’s code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |