Detect the snapshot key to be compare with using Git hash.
Complete git topic and scope from history
autocomplete plugin for oclif
A Node.js library for interacting with the Vercel Queue Service API
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
Dependency free publish/subscribe library
The Instana Node.js metrics and trace data collector
Confluent Schema Registry implementation in javascript to easily serialize and deserialize kafka messages
Validator component for Vue.js
An isomorphic client library for the Azure Event Grid service.
deploy and retrieve commands for sf
Parse and generate MQTT packets like a breeze
Calendar! with events
IEEE 754 half-precision floating-point for JavaScript
PubSub interface for libp2p
Commands to interact with Users and Permission Sets
Commands to interact with Salesforce agents
Commands to create metadata from a default or custom template
Commands to interact with salesforce sobject schemas
plugin for sf auth commands
Match mqtt formatted topic strings to strings
commands to display api limits to your org
Plugin for salesforce data commands
Get raw git commits out of your repository using git-log(1).
gem command around reviewed topic branches. Supports workflow of the form: # alexander: git work-on <topic> git done # bismarck: git status # notice a review branch git review <topic> # happy, merge into master, push and cleanup git accept git review <topic2> # unhappy git reject # alexander: git status # notice rejected topic git work-on <topic> see README.rdoc for more (any) details. To make use of bash autocompletion, you must do the following: 1. Make sure you source share/completion.bash before you source git's completion. 2. Optionally, copy git-topic-completion to your gem's bin directory. This is to sidestep ruby issue 3465 which makes loading gems far too slow for autocompletion.
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.
provides a set of git workflow tools to start and finish Pivotal Tracker stories in topic branches
Save your work. $ wipit > git add . && git rm $(git ls-files --deleted) && git commit -m 'WIP' Save your work to a topic branch. $ wipit my_wip_branch > git checkout -b my_wip_branch && git add . && git rm $(git ls-files --deleted) && git commit -m 'WIP' Save your work to a topic branch and push to origin. $ wipit my_wip_branch -p > git checkout -b my_wip_branch && git add . && git rm $(git ls-files --deleted) && git commit -m 'WIP' && git push origin my_wip_branch
Provides a set of git workflow tools to start and finish Pivotal Tracker stories in topic branches
= rails_vcstatus_logger It adds current state of version control to the log when you start the server. * Currently only supports git Adds current version hash and result of `git diff` The idea is that you can be sure about what source was running when you look in the log. I recently had a situation where i wasn't sure when a change was put up on the live server. Please add support for your vc system and send me a pull request! Just add this to enivorment.rb config.gem 'bjornblomqvist-rails_vcstatus_logger', :lib => 'rails_vcstatus_logger', :source => 'http://gems.github.com' == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2009 Bjorn Blomqvist. See LICENSE for details.