Get the latest push of a GitHub user.
Provides an API to fetch push notification tokens and to present, schedule, receive, and respond to notifications.
Push an array of items into an array, while being robust against prototype modification
Common typings for the Stoplight ecosystem.
A secrets manager for .env files – from the same people that pioneered dotenv.
Linter for the JavaScript Oxidation Compiler
<!-- BADGES -->
Formatter for the JavaScript Oxidation Compiler
Base parse-server-push-adapter
Web Push library for Node.js
Generate Beautiful Changelogs using Conventional Commits
amplify-cli authentication plugin
TypeScript definitions for web-push
amplify-cli storage plugin
Oxc Resolver Node API
[](http://www.typescriptlang.org/) [](https://www.npmjs.com/package/@n1ru4l/push-pull-async
Send samples to prometheus via remote_write from NodeJS
amplify-cli analytics plugin
React Native plugin for the CodePush service
amplify-cli function plugin
A fast fifo implementation similar to the one powering nextTick in Node.js core
UnRS Resolver Node API
Amplify CLI API Category Plugin
amplify-cli interactions plugin
Fetches the latest repository from the server, rebases/merges the current branch against the changes in the integration branch, then pushes the result up to a branch on the server of the same name. (Unless told not to.)
Fetches the latest repository from the server, rebases/merges the current branch against the changes in the integration branch, then pushes the result up to a branch on the server of the same name. (Unless told not to.)
Fetches the latest repository from the server, rebases/merges the current branch against the changes in the integration branch, then pushes the result up to a branch on the server of the same name. (Unless told not to.)
Fetches the latest repository from the server, rebases/merges the current branch against the changes in the integration branch, then pushes the result up to a branch on the server of the same name. (Unless told not to.)
Rules for linting Rails code at Panorama Education. Use the latest git commit of this gem instead of the version pushed to RubyGems.
Recreates a specified Git tag every time you deploy, with whatever codebase just got pushed live. This tag is used alongside another system, to deploy the latest production code to a newly autoscaled instance.
Rules for linting Ruby code at Panorama Education. Use the latest git commit of this gem instead of the version pushed to RubyGems.
This tool 1. create's a new branch 2. runs 'bundle update' 3. find's the latest patch-level version of Ruby and updates files that reference the version 4a. commit's the updates and pushes to gitlab, creating a new merge request 4b. delete's the branch if no updates were made
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.
= 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.
# Error `Error` is a very small library that serves as a base `Class` for error `Class`es within your application. ## Install ### Bundler: `gem 'error'` ### RubyGems: `gem install error` ## Usage ```ruby ``` ## Contributing * 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 © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details.
= epubforge = Write your book in markdown, then do all sorts of increasingly nifty things with it using this command-line utility. == Project description == epubforge is a command-line utility for creating, tracking and managing longer (novella and book-length) writing projects. Write your text in markdown (http://whatismarkdown.com/), use the built in actions to convert your project to various ebook formats, track wordcount over the life of the project, manage a story bible, and back your project up using git. Or go further and define your own formatters/converters and actions in Ruby. Have fun! == Contributing to epubforge == * 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 Bryce Anderson. See LICENSE.txt for further details.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.