A streamlined CLI tool to handle the heavy lifting of feature branch workflows. Stop typing long Git commands and let `git-thing` manage your branching, switching, and rebasing.
a util for spawning git from npm CLI contexts
Wrap Streams2 instance into a HandleWrap
Utility for dealing with modified, created, deleted files since a git commit
walk paths fast and efficiently
AWS IoT Node.js SDK for Embedded Devices
Automatically install pre-commit hooks for your npm modules.
Fix broken node modules with no fuss
Detect if we were run as a result of `npm publish`
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
Merge objects using their property descriptors
Defines all default Solana RPC subscriptions as types
Minimal module to check if a file is executable.
Parse, Resolve, and Dereference JSON Schema $ref pointers
Get raw git commits out of your repository using git-log(1).
A quick & dirty Gradle build file to JavaScript object parser
node wrapper around clang-format
vlts Error.cause convention
A ridiculously light-weight argument validator (now browser friendly)
Microsoft sucks
Simple GIT interface for node.js
a util for spawning git from npm CLI contexts
TypeScript definitions for kind-of
A high level git url parser for common git providers.
a Rack and Git based wiki like thing
Lightweight git project tool.
dotstore is an easy way to keep your dotfiles in sync between computers, using git for all the things that make sense to use git for, and scripts for the rest.
When you need to git things done on multiple local repositories.
GitParty is a mushin-based DSF for doing all Git things
A set of patches to Ruby MRI 1.9.3 and 1.9.2 that adds run-time introspection, a call frame object, and other run-time support for things like debuggers. Necessary patches and some simple patch code are found in the git repository. See https://github.com/rocky/rb-threadframe/wiki/How-to-Install for how to install.
Provides an SCM agnostic way to manage subprojects with a workflow similar to the scm:externals feature of subversion. It's particularly useful for rails projects that have some plugins managed by svn and some managed by git. For example, "ext install git://github.com/rails/rails.git" from within a rails application directory will realize that this belongs in the vendor/rails folder. It will also realize that this URL is a git repository and clone it into that folder. It will also add the vendor/rails folder to the ignore feature for the SCM of the main project. Let's say that the main project is being managed by subversion. In that case it adds "rails" to the svn:ignore property of the vendor folder. It also adds the URL to the .externals file so that when this project is checked out via "ext checkout" it knows where to fetch the subprojects. There are several other useful commands, such as init, touch_emptydirs, add_all, export, status. There's a tutorial at http://nopugs.com/ext-tutorial The reason I made this project is that I was frustrated by two things: 1. In my opinion, the workflow for svn:externals is far superior to git-submodule. 2. Even if git-submodule was as useful as svn:externals, I would still like a uniform way to fetch all of the subprojects regardless of the SCM used to manage the main project.
Faster, safer git branching.
Continuous integration should really just be a script that captures the output of running your project update & test commands and presents recent results in a static html page. By keeping test reports in json, per-project CI configuration in 3 probably-one-line scripts, things are kept simple, quick, and super extensible. Want to use git, svn, or hg? No problem. Need to fire off results to Campfire? It's built-in. CI depends on cron.
# PaApi A simple wrapper for the Parallels Automation APIs. ## Installation Add this line to your application's Gemfile: ```ruby gem 'pa_api' ``` And then execute: $ bundle Or install it yourself as: $ gem install pa_api ## Usage Just use the damn thing already. ## Contributing 1. Fork it ( https://github.com/[my-github-username]/pa_api/fork ) 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create a new Pull Request
Continuous integration should really just be a script that captures the output of running your project update & test commands and presents recent results in a static html page. By keeping test reports in json, per-project CI configuration in 3 probably-one-line scripts, things are kept simple, quick, and super extensible. Want to use git, svn, or hg? No problem. Need to fire off results to Twitter or Campfire? It's one line away. CI depends on cron.
A Successful Deployment Ends Peacefully With No Bullets Fired. If That’s Simply Not Possible, SWAT Uses Special Weapons and Tactics to Keep the Public Safe GitLab-Swat allows admins to quickly deploy scripts that can be remotely executed through a rails console Enabling fast action by using an external git repository as the scripts source, but keeping safety high by enforcing a prepare-pre check-execute model that allows execution break at any stage if things are not going as expected
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.