A NodeJS library to launch editor like Git does.
Lint files staged by git
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
A pure JavaScript reimplementation of git for node and browsers
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
CSS Object Model implementation and CSS parser
semantic-release plugin to commit release assets to the project's git repository
PM2.io Agent Standalone for NodeJS
Parse the things that can be arguments to `npm install`
Prebuilt libvips and dependencies for use with sharp on Linux (glibc) x64
> Rewrite a WASM binary
Prebuilt libvips and dependencies for use with sharp on Linux (musl) x64
Image Edit Plugin for FilePond
Efficient Git Commit Message Linting and Formatting
Git Implemented in JavaScript
Enhance your conventional commits with gitmoji
CSS Object Model implementation and CSS parser
CSS Object Model implementation and CSS parser
Flmngr file manager UI component for React
Get raw git commits out of your repository using git-log(1).
library to do the things that 'npm version' does
The Polymer library makes it easy to create your own web components. Give your element some markup and properties, and then use it on a site. Polymer provides features like dynamic templates and data binding to reduce the amount of boilerplate you need to
Simple yet powerful framework for building command-line apps.
Parse repository URLs to extract, SCM platform, domain, user, and project information.
git-topic enables you to manage your topic branches by simple sub commands like "git topic (list/edit/show)". This sub commands use branch description.
RNote is a command line tool for accessing Evernote. You can use it to find, create, and edit notes directly on the Evernote Cloud. RNote will launch your own EDITOR when you ask to edit a note. Much like git does for commit messages.
Local AI coding agent with abilities like: File editing with diffs, Git command approvals, Model switching, Repo awareness. All on your machine available offline
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
No description provided.
No description provided.
No description provided.
No description provided.