Datadog CI plugin for `dora` commands
Sink your streams.
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
Unique tag for use in the type-fest Tagged type
Manage your projects version through just a git tag
A join-coefficients-fixed mediator
multihash implementation
Cedar believes the future is serverless and multi-client. And `@cedarjs/api` makes Cedar serverless and multi-client ready. Cedar has one API to rule them all. Your API is abstracted away from any one side of your application, so you can have as many side
Offload tasks to a pool of workers on node.js and in the browser
Crypto primitives for libp2p
No description provided.
Git command to transform staged files according to a command that accepts file content on stdin and produces output on stdout.
IPFS Peer Id implementation in Node.js
No description provided.
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
Harness-agnostic git shim for CLEO agent branch-protection (T1118)
semantic-release plugin to back-merge a release into a develop branch
A CLI utility to add SOTA and POTA references to an existing ADIF file
No description provided.
Sync Claude Code sessions between machines with automatic path remapping and skill conversion
React Responsive Carousel
Tiny tool to run commands for modified, staged, and committed git files.
Native navigation primitives for your React Native app.
Get raw git commits out of your repository using git-log(1).
Show the lead time of branches merged into the current branch.
There are tons of books yelling about how you shouldn't repeat yourself, how you should keep it DRY(Don't Repeat Yourself). Well, we tried hard to keep the code clean, but when it comes to blog we wrote, we seems quite ignorante to the DRY principle. During the whole developement process, there will always be some interesting points you want to record, so git gurus told us to write proper git commit messages for further reference or so. And yes, I followed, and I spent quite a time writing about the problem I encountered, how I found the solution, and what should might be useful in the future. That's nice, right? But I've also got a blog to write! Wait, I don't want to REPEAT MYSELF. And that leads to a barely touched blog site. And git-blog is here to help.