Simple GIT interface for node.js
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
Adds App version number to Ember Inspector Info Tab
Get raw git commits out of your repository using git-log(1).
Create Next.js-powered React apps with one command
Get all git semver tags of your repository in reverse chronological order.
Git describe information at runtime, with semver support
Simple git client for conventional changelog packages.
semantic-release plugin to commit release assets to the project's git repository
Clean an input string into a usable git ref
List of Git hooks
A high level git url parser for common git providers.
A low level git url parser.
Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com
A pure JS SHA1 implementation created for js-git.
Create a new Open Mercato application
GitHub API token authentication for browsers and Node.js
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
Management SDK for the CodePush service
Set your Tauri application as the default handler for an URL
Resolve the path to the user's local or global .gitconfig.
JavaScript build tool, similar to Make or Rake
Download templates and git repositories with pleasure!
Datadog CI plugin for `dora` commands
Show version number based on git commit counts and enable to show change log from commit messages
Manage your app version entirely via git tags
Automatically map android app version to git tags
Adds version and git information overlays to your iOS app icon
Manage your app version entirely via git tags (even lite tags)
With this gem you can generate a changelog using Pull Requests logs on your local branch
Adds a page to your app for verifying the version of the code currently running. It displays the log of the last git commit.
Rain is a single-command deployment engine for Rails applications. It defines a set of conventions for deploying the same app version to multiple servers in multiple environments. Leveraging Git tags, it automatically increments versions according to the Semantic Versioning standard and deploys those versions using Capistrano to as many servers and environments as you wish."
== Jiveapps These tools are all about making Jive App development as easy as possible. After you install the tools, it only takes a single command to: 1. Create a new app - a simple Hello World application. 2. Set up version control for your code using Git. 3. Host the app code online at Jive's AppHosting server. 4. Register the app on the Jive Apps Marketplace as an app "in development". 5. Install the app on your default app dashboard in the Jive Apps Sandbox. After you install, use this simple workflow to make changes and see them reflected in the sandbox: 1. Make a change to the code on your local machine. 2. Commit the changes to your local Git repository. 3. Push the changes to the remote Jive Apps repository. This automatically updates the hosted copy on the Jive AppHosting server. 4. Refresh the app dashboard or canvas page on the Jive Apps Sandbox and see your changes. Other features: * LiveDev: preview your changes on the Jive App Sandbox in real time * Collaboration: add other developers to your project * OAuth Key Management: associate consumer key/secret pairs with service names for use in your apps
Envsafe is a standalone CLI utility for managing your .env files without project integration. Quickly back up your current environment, restore from any saved version, and compare your .env file against .env.example to catch missing or extra variables. Think of it as git stash for your .env. Core features: - Backup and restore .env files with optional tags - Pop the latest backup off the stack - Checkout any saved .env version or return to main - Validate .env vs .env.example - CLI-native — no Gemfile or code integration required Envsafe gives you safe, versioned control of your app’s environment variables — without the overhead.
# FaradayError [](https://badge.fury.io/rb/faraday_error) A [Faraday](https://github.com/lostisland/faraday) middleware for adding request parameters to your exception tracker. ### Supports - [Honeybadger](https://www.honeybadger.io/) - [NewRelic](http://newrelic.com/) - Your favorite thing, as soon as you make a pull request! ## Installation Add this line to your application's Gemfile: ```ruby gem 'faraday_error' ``` And then execute: $ bundle Or install it yourself as: $ gem install faraday_error ## Usage Configure your Faraday connection to use this middleware. You can optionally specify a name; defaults to `faraday`. It is expected that you also use `Faraday::Response::RaiseError` somewhere in your stack. ```ruby connection = Faraday.new(url: 'http://localhost:4567') do |faraday| faraday.use FaradayError::Middleware, name: "example_request" faraday.use Faraday::Response::RaiseError faraday.adapter Faraday.default_adapter end ``` And that's it. Make a request as you normally would. ```ruby connection.post do |req| req.url '/503' req.headers['Content-Type'] = 'application/json' req.body = JSON.generate(abc: "xyz") end ``` If any request fails, Honeybadger's "context" for this error will include your request parameters. If sending JSON or `application/x-www-form-urlencoded`, these will be included in parsed form. ```json { "example_request": { "method": "post", "url": "http://localhost:4567/503", "request_headers": { "User-Agent": "Faraday v0.9.2", "Content-Type": "application/json" }, "body_length": 13, "body": { "abc": "xyz" } } } ``` ## Development After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). The included [RestReflector](../master/spec/rest_reflector.rb) Sinatra app is suitable for making requests that are guaranteed to fail in particlar ways. ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/jelder/faraday_error. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. ## License The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
# Soft Delete > In a production app, you should probably never really delete anything. [source](https://twitter.com/theebeastmaster/status/966870021099180034) A soft-delete marks a record as deleted, and keeps it in the database for historical reference. ## Installation Add this line to your application's Gemfile: ```ruby gem "soft_delete-workbar", require: "soft_delete" ``` And then execute: $ bundle Or install it yourself as: $ gem install soft_delete-workbar ## Usage Safely "delete" records from your database without losing them permanently. * Add SoftDelete to a model ``` class MyModel < ActiveRecord::Base include SoftDelete end ``` * Add a `deleted_at` column to the model's database table ``` rails g migration AddSoftDeleteToMyModels deleted_at:timestamp ``` * Safely call `MyModel#delete` without losing the record forever ## Methods Please see the `SoftDelete` module and the associated tests for a description of the methods that will be added to your model. * `.not_deleted` - records without a deleted_at timestamp * `.deleted` - records with a deleted_at timestamp * `#delete` - set the deleted_at timestamp * `#delete!` - delete the record from the database * `#destroy` - set the deleted_at timestamp, and run callbacks * `#destroy!` - delete the record from the database, and run callbacks * `#restore` - set the deleted_at timestamp to nil It will be necessary to exclude deleted records when querying the model. Use the `not_deleted` scope that now exists on the model. ```ruby class MyModelsController < ApplicationController def index @my_models = MyModel.not_deleted end end ``` ## Development After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/workbar-dev/soft_delete. ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
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.