A tool to manage versioning and changelogs with a focus on monorepos
Introducing Changelog 2.0
**I'm excited to finally be able to introduce you to Changelog 2.0! This might seem like a simple visual update, but trust me when I tell you this is literally the biggest launch we’ve ever done.** tl;dr — we launched a new brand and CMS to power the future of our platform. !new-changelog-logo.jpg
Changelog.com is open source
This morning we open sourced the code that powers the new Changelog.com!
Universal Version Control
Building tools to help people explore alternatives, keep track of history, and collaborate better, across all kinds of media.
panproto | schematic version control
One engine for schematic version control within and across any schema language.
v2 Editor Manifesto
The manifesto for our brand new rich text editor with version control capabilities, v2. In this post, we describe the basic principles, design decisions and our vision for v2, alongside reflecting on the current state and potential future of knowledge production in society.
01 · Universal version control
We believe that simple, powerful, universal version control tools could help all kinds of creators produce better work.
Redesigning source control at Anthropic
As our merges per day grew more than tenfold, source control became our biggest development bottleneck. Here, we share how we migrated to an in-house version control system in five months.
panproto/panproto
One engine for schematic version control within and across any schema language.
Build a Versioning System With IPFS and Blockstack
There are so many great use cases for versioning. Handling code deployments, document edits, and database snapshots are just a few…
A Categorical Theory of Patches
When working with distant collaborators on the same documents, one often uses a version control system, which is a program tracking the history of files and helping importing modifications brought by others as patches. The implementation of such a system requires to handle lots of situations depending on the operations performed by users on files, and it is thus difficult to ensure that all the corner cases have been correctly addressed. Here, instead of verifying the implementation of such a system, we adopt a complementary approach: we introduce a theoretical model, which is defined abstractly by the universal property that it should satisfy, and work out a concrete description of it. We begin by defining a category of files and patches, where the operation of merging the effect of two coinitial patches is defined by pushout. Since two patches can be incompatible, such a pushout does not necessarily exist in the category, which raises the question of which is the correct category to represent and manipulate files in conflicting state. We provide an answer by investigating the free completion of the category of files under finite colimits, and give an explicit description of this category: its objects are finite sets labeled by lines equipped with a transitive relation and morphisms are partial functions respecting labeling and relations.
There Are No Bugs, Just TODOs | Almad's Changelog
One of my life’s traumas is the bug trackers, the issue trackers, the project management tools. The toolset that completes the version control log to form the development equivalent of double-entry bookkeeping.
So we don't usually make version update posts but this is a bit of a special one. We just released v0.6.7 which in and of itself isn't immensely interesting, it's a very bug fix heavy release just like v0.6.6. A lot of those bug fixes should fix compatibility with some apps namely Colibri. But ...
