A simple object to watch for git repo changes and update the local code
Get the remote origin URL of a Git repository
JS/WebAssembly build of OpenJPH
Yjs encoding protocols
Appium proxy for Remote Debugger protocol
Get tags from a remote Git repo
Shared utilities for Paperclip adapters: process spawning, environment injection, sandbox/SSH transport, workspace sync, and the round-trip helpers that move code between the local execution-workspace cwd and wherever the agent actually runs.
semantic-release plugin to commit release assets to the project's git repository
Fetches and manages remotely-hosted assets and updates to your app's JS bundle.
Get remote repository tags.
A secrets manager for .env files – from the same people that pioneered dotenv.
CLI tool for converting Markdown files to PDF.
Get the git remote origin URL from your local git repository. Remember! A remote origin must exist first!
git plugin for meta
Deno namespace shim for Node.js
Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com
Command line tool for generating a changelog from git tags and commit history
Git/Subversion/Mercurial repository metadata parser
VSCode oniguruma bindings
Collects Git commit info from CI or from CLI
Tool for running ESLint on multiple repositories
Flagsmith lets you manage features flags and remote config across web, mobile and server side applications. Deliver true Continuous Integration. Get builds out faster. Control who has access to new features.
The Remote Config package of the Firebase JS SDK
middleware of FLOWFACT to interact between frontend and backend
A simple client library to remotely access the Sailthru REST API. Updated with latest git master.
GitRunner is a ruby framework to implement and run tasks after code has been pushed to a Git repository. It works by invoking `git-runner` through `hooks/post-update` in your remote Git repository.
RightScraper provides a simple interface to download and keep local copies of remote repositories up-to-date using the following protocols: * git: RightScraper will clone then pull repos from git * SVN: RightScraper will checkout then update SVN repositories * tarballs: RightScraper will download, optionally uncompress and expand a given tar file On top of retrieving remote repositories, right_scraper also include "scrapers" that will analyze the repository content and instantiate "resources" as a result. Currently supported resources are Chef cookbooks and RightScale workflow definitions.
Installs 5 commands that process a git directory tree. Directories containing a file called .ignore are ignored. The git-commitAll command commits all changes to each repository in the tree. The git-evars command writes a script that defines environment variables pointing to git repos. The git-exec command executes a bash expression on children of a directory, or a list of directories. The git-replicate command writes a script that clones the repos in the tree, and adds any defined remotes. The git-update command updates each repository in the tree.
= RUGS - RUby Git Setup A helper script that makes setting up remote git repositories a snap. == WARNING: This is still alpha so use it at your own risk! Note: I don't use alpha/beta in the version numbers until I have a first real release because of how Ruby Gems handles them. == What is it? RUGS has three main functions: * Creates a local git repository and directory structure using default templates or ones you create. * Sets up a remote repository to mirror your local one. * Adds a framework of git hooks allowing you to store and run your own hooks in directly from the repo. RUGS makes creating remote repos as simple as `rugs create repo_name on server_name`. RUGS even allows you to automatically embed your Git hooks in the repo itself. No more jumping through hoops to make sure your hooks are maintained with your project; with RUGS you just store your hook scripts in the `git_hooks` directory and they're automatically updated and run. \ Once you've set up your project using RUGS you just use Git as you normally would with the exception of your hooks being the in `git_hooks` directory.
== 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
# Dotbot: A Cute Lil' Dotfiles Manager I made a simple little dotfiles manager because I got tired of creating symlinks all the time. ## Installation You can install `dotbot` via the `gem` command: $ gem install dotbot Once you have it installed, either create a `~/.dotbot` file (YAML) with the following contents. ``` dir: ~/.dotfiles # or whatever your preferred location is ``` Optionally, instead of a .dotbot file, you can use environment variables, each of the pattern DOTBOT_<var>. For instance, you could execute some commands by saying $ DOTBOT_DIR=~/shnargleflorp dotbot update More commands and options to come later. ## Usage ### Track a New File $ dotbot track <filename> [--git] This command adds the file to your dotfiles repo and creates a symlink in the file's old location so it will stay updated. Use the `--git` flag to also add/commit/push to your remote dotfiles repo. ### Update Your Dotfiles $ dotbot update This command is pretty much just a `git pull` in your dotfiles repo. ## Development After checking out the repo, run `bin/setup` to install dependencies. 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/[USERNAME]/dotbot-mini. 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](https://opensource.org/licenses/MIT). ## Code of Conduct Everyone interacting in the Dotbot::Mini project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/rpalo/dotbot/blob/master/CODE_OF_CONDUCT.md).
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.