🚀 Flexible commit message templating from branch name (ticket/segments) for Husky's prepare-commit-msg hook. Automatically extracts Jira-style tickets and supports customizable templates.
Common typings for the Stoplight ecosystem.
<!-- BADGES -->
AWS SDK for JavaScript Codecommit Client for Node.js, Browser and React Native
To get started, use the following command as your [Ignored Build Step](https://vercel.com/docs/concepts/projects/overview#ignored-build-step):
Generate a changelog from git metadata.
Handles making a GitHub branch with the commits from a memfs instance or a file map
Web framework built on Web Standards
Detect the snapshot key to be compare with using Git hash.
Straightforward project scaffolding
An implementation of the Infra Living Standard
Git commit, but play nice with conventions.
semantic-release plugin to analyze commits with conventional-changelog
Collects Git commit info from CI or from CLI
Read details of the last commit including tags
Module for reading .pgpass
Husky Git hook to add JIRA ticket ID into the commit message
semantic-release plugin to commit release assets to the project's git repository
tiny commit walker
replacement for `npm version` with automatic CHANGELOG generation
A formatter collection for Secretlint.
Get all git semver tags of your repository in reverse chronological order.
Automatically install pre-commit hooks for your npm modules.
An implementation of the URL Living Standard
A Ruby script for git that finds what branch a commit came from.
The will_paginate library provides a simple, yet powerful and extensible API for pagination and rendering of page links in templates. This version is from agnostic branch. commit : e0b094f44cf39e704f9862c708b202d331604cf7
Caperoma automates many decisions related to the programming that you often don't realize, and which you can forget hundreds of times during the time of working on the project: pulling the latest code from upstream before you start working, remembering from which branch you started the feature to later make a pull request into it, creating & starting tasks in Jira, creating & starting tasks in Pivotal, naming branches, adding Jira ID into the branch name, style guide checks, commits, naming commits, adding Jira ID into commit name, adding Pivotal ID into commit name, git pushes, pull requests into correct branches, stopping tasks in Jira, stopping tasks in Pivotal, tracking time, logging time to Jira, switching back into the original branch and much more.
Most useful for squash merge commits on Github - this gem links pull request from each commit between two branches, and extracts information from pull request.
Automate the generation of Turnip/RSpec specs from Notion tickets, create branches, commits, pushes, and GitHub Pull Requests. All with a single Rake command.
This is the workflow we use when developing zena. The main idea is that developers work on feature branches on their fork and send an email to the reviewer when work is ready. The reviewer pulls from these branches, checks that all is good and either apply the commits to the gold master or abort. There is a script called 'gold' that helps use this workflow once the remote references are added. Any questions ? Ask zena's mailing list: http://zenadmin.org/en/community ~~
A lightweight Ruby gem that helps create conventional commit messages by automatically extracting ticket numbers from branch names
Helpers to read debian control files
Quickly copy files (e.g. YMLs or configuration files) to multiple EngineYard servers
# EventReporter EventReporter is a CSV parser and sorter. you can load a CSV and then search it. ## Installation $ gem install the_only_event_reporter_ever $ gem list event_reporter -d ## Usage After installation run: $ event_reporter Then Type 'load <filename>' to load records from a CSV $ Load event_attendees.csv Try these commands $ Find first_name sarah $Queue Print $Queue Save to <filename> ### Saving the queue accepts extensions JSON, XML, TXT, CSV. ## Contributing 1. Fork it 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 new Pull Request
= wahlrecht_de Provides summary analysis of current poll results from wahlrecht.de == Contributing to wahlrecht_de * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet. * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it. * Fork the project. * Start a feature/bugfix branch. * Commit and push until you are happy with your contribution. * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it. == Copyright Copyright (c) 2013 Tobi Fankhänel. See LICENSE.txt for further details.
# Rack::ReadOnly This gem allows Rack based APIs to be set to read only. At the most basic it can be used like this from your `config.ru`: ```ruby require 'rack/read_only' use Rack::ReadOnly, { active: ENV["READ_ONLY"] == "1", response_body: '{ "error": "This API is currently in read only mode." }' } run MyApp ``` When in read only mode the API will continue to respond to GET, HEAD, and OPTIONS requests as normal, but reject POST, PUT, DELETE, and PATCH requests with the body specified, and a 503 error code. ## Installation Add this line to your application's Gemfile: ```ruby gem 'rack-read_only' ``` And then execute: $ bundle Or install it yourself as: $ gem install rack-read_only ## Development After checking out the repo, run `bin/setup` to install dependencies. 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` to create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing 1. Fork it ( https://github.com/jellybob/rack-read_only/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 Any new builds should pass the tests on [Travis](https://travis-ci.org/jellybob/rack-read_only)
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.