Digest Diff

Let commit history tell its story with AIEvery codebase’s commit history holds an untold story of progress, collaboration and evolution. DigestDiff helps you tell those stories—privately—with AI-driven tools which rely only on commit history, not code.Get a codebase overviewWeave the breadcrumbs left by commits into a detailed narrative, offering a clear, succinct and informative summary of a codebase. Uncover the story behind the commit log, get insight into the authors’ contributions, and trace the evolutionary journey of the code over the time.Accelerate onboarding. Step into the shoes of past developers and get up to speed with a codebase in minutes.Let history tell its story. Commit history is a rich source of information which can be unlocked with a detailed overview.Save and share. Overviews can be exported as markdown, ready to be shared and discussed with your team.Let your codebase tell its story →Recap your recent workRemembering what you had for breakfast is hard enough, let alone what you did yesterday or last week. Succinctly and accurately summarise the work you’ve been doing in a format perfect for your standups, retrospectives, and weekly reports.Save time. You've already done the work once; let the power of AI summarise it for you.Perfect recall. Never fumble your way through an update again - recap your changes and get back to work.Easily exportable. Copy and paste the plain text or markdown version of your update to easily share with your team.Get an instant standup update →Create release notesStreamlined, intuitive, fast. Leverage your git commit history to create detailed, informative release notes—without ever accessing your code. Tap into the power of AI to automate your release notes and free up your team to focus on creating great software.You set the tone. Tweak the writing style, personality, tone, length and more: let the AI do the rest.Private and secure. Commits are securely pulled from GitHub and never stored on our servers. No code is ever accessed.Export as markdown. After reviewing and refining your release notes, export them ready for distribution.Reimagine your release notes →Privacy firstKeep your code out of itPrivacy is built into the core of Digest Diff from the ground up. We’re committed to providing insightful tooling while keeping your sensitive data secure:Read-only access: We only ever request read-only access to your GitHub repositories. If we could request even less access—limited to just commit history—we would.Commit history only: We only need one thing to do our thing: your commit history. We will never access any code. Ever.Store nothing: We don’t ever log or save any generated release notes or codebase overviews. You can choose to export them, but we don’t store them.Get startedTry for free on public or private GitHub repositoriesYou’ll get 5 free credits when signing in for the first time which you can use on any of the tools with commit history from a private GitHub repository, a public GitHub repository, or manually entered commit history.IntegrationsConnect with GitHub when you’re readyWhat could prove that we don’t touch code better than allowing you to manually paste in a git log instead of connecting with GitHub? Manually submitting commit history works in exactly the same way as fetching it from GitHub—it just requires a little more effort.Anything else?Frequently asked questionsYou can find the most frequently asked questions about Digest Diff on a dedicated FAQ page. If you still want to know more or get in touch, use the Feedback navigation link or follow the footer link to find me.As seen on…Dang!FindAITools --- ExamplesEverything on this page was generated on digestdiff.com and has not been hand-edited in even when it was tempting to do so. These examples aren’t perfect, but they’re here to show what you can realistically expect from your own release notes and codebase overviews.Release notesbootboxjs/bootboxDiffv5.5.3...v6.0.0PersonalityEnthusiasticLengthLongOther settingsDefaultsBootbox v6.0.0 Release Notes We are excited to announce the release of Bootbox v6.0.0! This major release brings a plethora of enhancements, bug fixes, and updates to the codebase. Our team has worked hard to ensure that this release is packed with features that will make your experience with Bootbox even better. Let's dive into the details! Major Enhancements Configurable error message for prompt: You can now customize the error message displayed for prompt dialogs (975a2b0). This new feature provides more flexibility in user interactions and improves the overall user experience. Improved modal header rendering: We've made significant improvements to the rendering of modal headers, ensuring that they are displayed correctly and consistently across different use cases (f6108a3, 1dc87a1, 6c7aded). Generating bootbox.locales.js from locale files: Bootbox now generates the bootbox.locales.js file from individual locale files, making it easier to manage and update translations (696fa33). Minor Enhancements Updated Bootstrap minimum version: The minimum version of Bootstrap required for Bootbox has been updated (f2d4acb). Added JSDoc comments: We've added JSDoc comments to improve code readability and maintainability (5bc956b). Created tests.yml: A new tests.yml file has been created to better manage and organize tests (0310471). Gruntfile updates: We've made several updates to the Gruntfile, streamlining the build process and improving overall efficiency (d51a0f1, c0541a7). Pattern fallback for date and time inputs: Bootbox now provides a pattern fallback for date and time inputs, ensuring better compatibility with different browsers (686963a). Dependency Updates We've updated several dependencies to ensure Bootbox stays up-to-date and secure: Bump grunt from 1.5.2 to 1.5.3 (fd1d1cc, b13f670) Bump terser from 4.4.0 to 4.8.1 (604d8b5, a2636ef) Bump socket.io-parser from 4.0.4 to 4.0.5 (865f904, b1b6bc6) Bump loader-utils from 1.2.3 to 1.4.2 (e79ca03, a3e79ef) Bump minimist and karma-mocha (d1d9447, 20fe788) Bump shelljs and grunt-contrib-jshint (3d91896, fb7edee) Bump engine.io and socket.io (9c6e990, ae1197d) Acknowledgements We would like to extend our gratitude to all the contributors who have made this release possible, especially Tieson Trowbridge for their significant contributions and dedication to the project. We would also like to thank dependabot[bot] and Jonathan Stark for their contributions to this release. Thank you for your continued support, and we hope you enjoy using Bootbox v6.0.0!Codebase overviewmakeusabrew/faavoriteTypeSummary + detailed historyThe 'faavorite' repository appears to be a codebase for a web application that deals with managing and displaying favorited tweets, user interactions, and various related features. The application integrates with Twitter API, Dribbble API, and other external services to fetch data and perform actions such as favoriting tweets, importing favorites, and resolving URLs. It also includes functionality for handling user accounts, displaying user profiles, handling tags, and generating events and notifications based on user interactions. The codebase has been actively developed by two main contributors, Nick Payne and Harry Roberts. Nick Payne has primarily worked on the back-end functionality, including integrating with external APIs, handling user accounts, and implementing the core logic for managing favorites and events. Harry Roberts has focused on the front-end, working on UI design, styling, and user experience improvements. Both developers have collaborated on various features and bug fixes throughout the development process. If the new developer needs help or guidance, they should reach out to Nick Payne for back-end related questions and Harry Roberts for front-end related questions. In the early stages of the 'faavorite' codebase, the focus was on setting up the basic structure and integrating with the Twitter API. Nick Payne started by adding simple methods to fetch the most favorited tweets and making the list of users who favorited a tweet dynamic (8cc4a40, fbf0ae0). The application then evolved to include checks for valid favorite objects, restricting the number of favorites displayed, and implementing the basic account markup (a10ebf1, 2d7e8b6, fd6fdd2). As the project progressed, the team expanded the application's functionality by integrating with other APIs such as Dribbble and GitHub (e70829a, 26437a4). They also improved the user experience by adding AJAX-based features, like adding comments, and introduced dynamic date handling in the footer (2feed8f, e90d79d). During this time, Harry Roberts focused on improving the UI and design, working on table of contents, markup, and miscellaneous UI additions (889f249, 9f72e71, af30957). The team also worked on optimizing the performance of the application, such as tweaking the sort order of favorites and handling errors from the Twitter API (563a461, 546496c). As the application matured, the team added more advanced features, like tracking outbound link clicks, implementing integration tests, and handling user mentions (4f58ebb, ae40f05, bbf523b). They also reworked the user profile logic and added features like user tags and friend favorites (6a49d73, 41f9582). Throughout the development process, the team continuously optimized the codebase by fixing bugs, improving performance, and refining the user experience. They addressed issues like UTF-8 encoding, optimizing feed queries, and updating the underlying libraries (174b5a7, a0ae7e4, 8942a1e). In the later stages of the project, the team worked on refining the user interface and experience. Harry Roberts made significant changes to the styling, layout, and design of various components, such as buttons, avatars, and notifications (c85dff6, 07cb8eb, 07ae6f7). Meanwhile, Nick Payne continued to improve the back-end functionality, adding features like random favorite generation and implementing more efficient URL resolution (00bc941, be66b99). In summary, the 'faavorite' codebase has evolved from a simple application focused on fetching and displaying favorited tweets to a more comprehensive and feature-rich platform that integrates with multiple APIs, offers a refined user interface, and provides an optimized user experience. The team has continuously improved the codebase by addressing bugs, refining existing features, and adding new functionality throughout the development process.Recapmakeusabrew/feedback-rocketMay 29th: Added manual CORS headers in API submit handler and noted that SendGrid doesn't work on edge runtime but will be moved Fixed trivial build errors introduced by package upgrades Added recommended 'sharp' image optimization package Moved email sending logic out of edge function, off critical path, into webhook callback handler Added a note about creating a notifications table (post merge) Renamed Supabase callback handler Took Feedback Rocket embed ID from environment variables Implemented very basic thank you/error widget feedback screens Paved the way for dynamic thank you messages Destructured response and made it dynamic from the server Merged pull request #9 (widget-feedback) and #10 (faster-submissions) into the main branch May 30th: Created notifications table Merged pull request #10 (faster-submissions) into the main branch Release notesmakeusabrew/chshDiffd919751...HEADPersonalityDefaultLengthDefaultOther settingsDefaultsChess Shell v2.0.0 Release Notes We are pleased to announce the release of Chess Shell v2.0.0. This release brings significant improvements to the game engine, AI, and overall performance. The following highlights the key features and enhancements introduced in this release. Features and Enhancements Game Engine Introduced game state management (501b82f) Implemented logic to test for checks after a move has been made (30b8dc9) Added support for castling, en passant, and promotion to all pieces (9eb832f, aaac542, dde8d57) AI Improvements Implemented basic AI functionality with iterative deepening (9eb832f, 8fbe9d8) Added support for multiple AIs per game (4439cf0) Introduced the concept of difficulty levels (6e1c753) Implemented quiescence search for more accurate move evaluations (ffb50c7) Performance Optimizations Switched to Chars and CharArray instead of Pieces and Map for better performance (d1ba7aa, 8027b5a) Optimized pawn movement and king attack calculations (d6d084f, 4430f1e) Pre-generated most legal moves to avoid repeated out-of-bounds checks (c50555a) User Interface Added support for serving static assets from the resources directory (27e5898) Implemented ASCII board rendering with 'x' instead of space (2d85bac) Bug Fixes and Refinements Fixed pin movement and castling logic (9331ff0, 274d55b, 456209c) Improved handling of draw by threefold repetition (dc705fc, 28bf123) Fixed calculation of state after move and undo (2368087) Contributors We would like to extend our gratitude to the following contributor for their work on this release: Nick Payne Please refer to the git log for a comprehensive list of changes in this release. We encourage users to update to Chess Shell v2.0.0 for an enhanced chess experience.Release notesmakeusabrew/paynedigital.comDiffv1.1.2...v2.0.3PersonalityDefaultLengthDefaultOther settingsDefaultsPD Website v2.0.3 Release Notes We are pleased to announce the release of PD Website v2.0.3. This release includes numerous improvements, bug fixes, and new features. We would like to express our gratitude to Nick Payne for his significant contributions to this release. New Features and Improvements Implemented PJAX support for smoother page transitions and improved user experience (3716d8d, 93c8c74, 5205cac) Added support for Firefox and ensured class transition is applied after delay (009da1a) Introduced new themes and improved theming for various sections (8674ce3) Implemented a rough and ready server-side Gist parser (84e7a06) Upgraded jQuery from 1.6.4 to 1.7.1 (c432ad6) Added recommended follow to tweet buttons (4974655) Implemented StatsD for logging and monitoring (5d99112, 4682c63) Reworked PD home page for improved layout and content organization (e2596e5, d1976ae) Bug Fixes Fixed back button not triggering new theme (1bfc749) Fixed incorrect label colors (52fd8bf) Fixed issue with tags containing spaces and numbers (7b9282f, 190ca4e) Changed ordering of posts from created to PUBLISHED (869110f) Fixed headless test issues and improved test coverage (6b569b0, cdb261a, 376b5e9) Fixed issue with content loaded by PJAX not scrolling to the top (b05d930) Miscellaneous Removed unnecessary JavaScript includes and optimized JS loading (9e3a41b, b408ba0) Updated JAoss library and submodule references (a2b6133, 2d662e6, a4a6fd3, 2232500) Tweaked copy, layout, and styling in various sections (577d1fe, faafb24, 59816dd, e572a4b) Thank you for your continued support, and we hope you enjoy the improvements and new features in PD Website v2.0.3. --- Frequently asked questionsI've already signed in with GitHub - why do I need to connect with GitHub again?Signing in provides basic GitHub profile details like your profile picture and email address which we use for authentication. Connecting a second time will request read-only private repository access - but please note this is totally optional and you can still use the site without it.The GitHub integration wants read-only repository access. Will you access my code?Absolutely not. We only use the GitHub integration to read commit history - it would actually be far better for us if GitHub offered more fine-grained access to request only that. Nevertheless, your code will never be accessed.I don't want to grant private repository access. Can I still use the site?Yes! You can still use all the tools with public GitHub repositories or by manually entering commit history.Can I try any of the tools for free?Absolutely! You need to sign in with GitHub first so we can track credit usage, but when you sign up you'll get 5 free credits to play around with each tool.How does pricing work?Digest Diff is pay-as-you-go. You buy credits, and those credits can be used on any of the tools. The more credits you buy upfront, the cheaper they are.What does a credit get me?Release notes and recaps are fixed at one credit per use. Codebase overviews let you choose between generating a basic summary (one credit) or detailed history (two credits).Credits seem to cost more than other AI tools. Why is that?Digest Diff makes exclusive and very extensive use of commit history. This typically involves sending a lot of 'context' to ChatGPT, and more context unfortunately costs more money. We're looking at ways we can make credit usage dynamic based on commit history to mitigate this.Is this just ChatGPT under the hood?Yes and no. The model at the heart of the system is indeed OpenAI's GPT-4, but a vast amount of effort has gone into choosing the right prompts for each tool, making those prompts adapt to the numerous choices you can make, not to mention fetching and squeezing as much commit history into the allowed context window for GPT-4 as possible.Do you store or inspect any generated recaps, overviews or release notes?Absolutely not. Responses are streamed directly to your browser: we do not log them nor store them. You may choose to export them once generated, but that's entirely up to you.My question wasn't answered here - how can I get in touch?Please use the Feedback navigation link and be sure to leave a return email address if you'd like a response. Alternatively follow the footer link to find various ways of contacting me. --- Codebase overviewPowered by AI, driven by commit history: weave the breadcrumbs left by commits into a detailed narrative, offering a clear, succinct and informative summary of your codebase. Uncover the story behind the commit log, get insight into the authors’ contributions, and trace the evolutionary journey of the code over the time. All this without ever accessing any actual code—just commit history. Codebase detailsYou can paste a GitHub repository URL like this anywhere on this page to pre-populate these fields. Try it with any public repository or a private repository you’ve granted access to.SourceEnter any GitHub repositorySelect from your GitHub repositoriesPaste a commit logGitHub repositoryProject nameOverview typeSummary only (1 credit)Summary + detailed history (2 credits)Sign in to startOne credit will be used as soon as your overview starts being generated. Another will be used when the detailed history begins—usually after one or two introductory paragaphs.You won’t be charged if your queued request cannot be processed for any reason.The dummy text shown here only gives you a very basic idea of how your overview will look. See the examples page for a better idea of what you’ll get.CloseThis repository contains solutions for the Advent of Code (AOC) programming challenges from various years, mainly focusing on the 2022 edition. Advent of Code is an annual event where developers solve daily programming puzzles throughout December. The solutions in this repository are implemented in multiple programming languages such as Rust, JavaScript, Elixir, Python, Scala, Kotlin, and Zig. The commit history shows the developer's progress as they work through the challenges, often mentioning struggles, improvements, and refactoring. The developer also occasionally goes back to previous years' challenges, such as AOC 2015 and AOC 2016, and solves them using different languages. In summary, this repository is a collection of programming solutions for the Advent of Code challenges, showcasing the developer's skills and experience in various programming languages. In the beginning, the developer focused on solving the Advent of Code (AOC) 2022 challenges, primarily using the Rust programming language. As they progressed through the daily puzzles, they made improvements to the codebase, such as better layout and reusability of input, adding comments for clarity, and optimizing the code by replacing certain functions with more efficient alternatives. The developer occasionally experimented with other programming languages like Muzzle, Zig, and JavaScript for some of the challenges. However, they often faced difficulties or were not satisfied with the results, describing the solutions as "terrible" or "dreadful." As the AOC 2022 event continued, the developer kept refining their solutions, addressing issues like off-by-one errors, simplifying match arms, and avoiding unwraps. They also tried to make the code more declarative and functional, using techniques like fold and filter_map. The developer occasionally switched between languages, implementing solutions in Elixir and JavaScript as well. After completing the AOC 2022 challenges, the developer moved on to solving challenges from previous years, such as AOC 2015 and AOC 2016. They used a variety of programming languages like Python, Scala, Kotlin, and Zig to solve these challenges, showcasing their versatility and adaptability. Throughout the process, the developer faced difficulties and struggled with some of the challenges, often resorting to brute force methods or writing "dirty" code to get the job done. However, they continuously made an effort to improve the codebase by refactoring, adding comments, and optimizing the solutions.Export your overviewYou can export your overview as many times as you want without cost.Please note that we do not save any generated content for security and privacy reasons, so please make sure you export them if you want to keep them.Download Markdown (.md)Copy markdown to clipboardCopy plain text to clipboard