huborg 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7aeb15386624a5bf1430e4fd989064ce84a04f4b88d760cc274db0defa21312d
+  data.tar.gz: 6d7b42c930fbbe776b97b022473133ea65e6faa89422532d7c5bf9559448c0fe
+SHA512:
+  metadata.gz: dac200b5c0d7cc50d6ec0f7d1db4b4ba43bc5f5e3330520e2f7f9f7b536742e43ae56d9ed73e3f513488fc81e77b6c530d0658cacc440b008d8cfe2cfeb05dee
+  data.tar.gz: 13c4e14c1d5c761e366c5c19715019aecbf8d8f643efde3bae158fddaa5280893e93647a5f6287ed1b9e1d1dbacca4ca887661b70056414b88e7f7b36c0d7d35

data/.gitignore

@@ -0,0 +1,12 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status
+Gemfile.lock

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+The Samvera community is dedicated to providing a welcoming and
+positive experience for all its members, whether they are at a formal
+gathering, in a social setting, or taking part in activities online.
+The Samvera community welcomes participation from people all over the
+world and these members bring with them a wide variety of
+professional, personal and social backgrounds; whatever these may be,
+we treat colleagues with dignity and respect.
+
+Community members communicate primarily in English, though for many of
+them this is not their native language. We therefore strive to express
+ourselves simply and clearly remembering that unnecessary use of
+jargon and slang will be a barrier to understanding for many of our
+colleagues.  We are sensitive to the fact that the international
+nature of the community means that we span many different social norms
+around language and behaviour and we strive to conduct ourselves,
+online and in person, in ways that are unlikely to cause offence.
+
+Samvera conversations are often information-rich and intended to
+generate discussion and debate.  We discuss ideas from a standpoint of
+mutual respect and reasoned argument.
+
+Community members work together to promote a respectful and safe
+community. In the event that someone’s conduct is causing offence or
+distress, Samvera has a detailed
+[Anti-Harassment Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
+which can be applied to address the problem. The first step in dealing
+with any serious misconduct is to contact a local meeting organizer,
+the
+[Samvera community helpers](https://wiki.duraspace.org/display/samvera/Samvera+Community+Helpers)
+([email](mailto:helpers@samvera.org)), a community member you
+trust, or the
+[Samvera Steering Group](https://wiki.duraspace.org/display/samvera/Samvera+Steering+Group+membership)
+immediately; at Samvera events, these people can be identified by
+distinctive name badges. The
+[Policy and Protocol](https://wiki.duraspace.org/display/samvera/Anti-Harassment+Policy)
+should be consulted for fuller details.

data/CONTRIBUTING.md

@@ -0,0 +1,161 @@
+# How to Contribute
+
+We want your help to make the Samvera community great. There are a few guidelines
+that we need contributors to follow so that we can have a chance of
+keeping on top of things.
+
+## Code of Conduct
+
+The Samvera Community is dedicated to providing a welcoming and positive
+experience for all its members, whether they are at a formal gathering, in
+a social setting, or taking part in activities online. Please see our
+[Code of Conduct](CODE_OF_CONDUCT.md) for more information.
+
+## Samvera Community Intellectual Property Licensing and Ownership
+
+All code contributors must have an Individual Contributor License Agreement
+(iCLA) on file with the Samvera Steering Group. If the contributor works for
+an institution, the institution must have a Corporate Contributor License
+Agreement (cCLA) on file.
+
+https://wiki.duraspace.org/display/samvera/Samvera+Community+Intellectual+Property+Licensing+and+Ownership
+
+You should also add yourself to the `CONTRIBUTORS.md` file in the root of the project.
+
+## Contribution Tasks
+
+* Reporting Issues
+* Making Changes
+* Documenting Code
+* Committing Changes
+* Submitting Changes
+* Reviewing and Merging Changes
+
+### Reporting Issues
+
+* Make sure you have a [GitHub account](https://github.com/signup/free)
+* Submit a [Github issue](https://github.com/samvera/{{library}}/issues/) by:
+  * Clearly describing the issue
+    * Provide a descriptive summary
+    * Explain the expected behavior
+    * Explain the actual behavior
+    * Provide steps to reproduce the actual behavior
+
+### Making Changes
+
+* Fork the repository on GitHub
+* Create a topic branch from where you want to base your work.
+  * This is usually the master branch.
+  * To quickly create a topic branch based on master; `git branch fix/master/my_contribution master`
+  * Then checkout the new branch with `git checkout fix/master/my_contribution`.
+  * Please avoid working directly on the `master` branch.
+  * You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
+* Make sure you have added sufficient tests and documentation for your changes.
+  * Test functionality with RSpec; Test features / UI with Capybara.
+* Run _all_ the tests to assure nothing else was accidentally broken.
+
+### Documenting Code
+
+* All new public methods, modules, and classes should include inline documentation in [YARD](http://yardoc.org/).
+  * Documentation should seek to answer the question "why does this code exist?"
+* Document private / protected methods as desired.
+* If you are working in a file with no prior documentation, do try to document as you gain understanding of the code.
+  * If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your pull request. You can use the 'blame' button on GitHub to identify the original developer of the code and @mention them in your comment.
+  * This work greatly increases the usability of the code base and supports the on-ramping of new committers.
+  * We will all be understanding of one another's time constraints in this area.
+* [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)
+
+### Committing changes
+
+* Make commits of logical units.
+* Check for unnecessary whitespace with `git diff --check` before committing.
+* Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+* If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
+
+```
+    Present tense short summary (50 characters or less)
+
+    More detailed description, if necessary. It should be wrapped to 72
+    characters. Try to be as descriptive as you can, even if you think that
+    the commit content is obvious, it may not be obvious to others. You
+    should add such description also if it's already present in bug tracker,
+    it should not be necessary to visit a webpage to check the history.
+
+    Include Closes #<issue-number> when relavent.
+
+    Description can have multiple paragraphs and you can use code examples
+    inside, just indent it with 4 spaces:
+
+        class PostsController
+          def index
+            respond_to do |wants|
+              wants.html { render 'index' }
+            end
+          end
+        end
+
+    You can also add bullet points:
+
+    - you can use dashes or asterisks
+
+    - also, try to indent next line of a point for readability, if it's too
+      long to fit in 72 characters
+```
+
+* Make sure you have added the necessary tests for your changes.
+* Run _all_ the tests to assure nothing else was accidentally broken.
+* When you are ready to submit a pull request
+
+### Submitting Changes
+
+* Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
+* Make sure your branch is up to date with its parent branch (i.e. master)
+  * `git checkout master`
+  * `git pull --rebase`
+  * `git checkout <your-branch>`
+  * `git rebase master`
+  * It is a good idea to run your tests again.
+* If you've made more than one commit take a moment to consider whether squashing commits together would help improve their logical grouping.
+  * [Detailed Walkthrough of One Pull Request per Commit](http://ndlib.github.io/practices/one-commit-per-pull-request/)
+  * `git rebase --interactive master` ([See Github help](https://help.github.com/articles/interactive-rebase))
+  * Squashing your branch's changes into one commit is "good form" and helps the person merging your request to see everything that is going on.
+* Push your changes to a topic branch in your fork of the repository.
+* Submit a pull request from your fork to the project.
+
+### Reviewing and Merging Changes
+
+We adopted [Github's Pull Request Review](https://help.github.com/articles/about-pull-request-reviews/) for our repositories.
+Common checks that may occur in our repositories:
+
+1. Travis CI - where our automated tests are running
+2. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
+
+If one or more of the required checks failed (or are incomplete), the code should not be merged (and the UI will not allow it). If all of the checks have passed, then anyone on the project (including the pull request submitter) may merge the code.
+
+*Example: Carolyn submits a pull request, Justin reviews the pull request and approves. However, Justin is still waiting on other checks (Travis CI is usually the culprit), so he does not merge the pull request. Eventually, all of the checks pass. At this point, Carolyn or anyone else may merge the pull request.*
+
+#### Things to Consider When Reviewing
+
+First, the person contributing the code is putting themselves out there. Be mindful of what you say in a review.
+
+* Ask clarifying questions
+* State your understanding and expectations
+* Provide example code or alternate solutions, and explain why
+
+This is your chance for a mentoring moment of another developer. Take time to give an honest and thorough review of what has changed. Things to consider:
+
+  * Does the commit message explain what is going on?
+  * Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
+  * Do new or changed methods, modules, and classes have documentation?
+  * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
+  * Does the description of the new/changed specs match your understanding of what the spec is doing?
+  * Did the Travis tests complete successfully?
+
+If you are uncertain, bring other contributors into the conversation by assigning them as a reviewer.
+
+# Additional Resources
+
+* [General GitHub documentation](http://help.github.com/)
+* [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
+* [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
+* [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in huborg.gemspec
+gemspec
+
+gem "rake", "~> 12.0"

data/LICENSE

@@ -0,0 +1,14 @@
+Copyright 2020 University of Notre Dame
+Additional copyright may be held by others, as reflected in the commit history.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,110 @@
+# huborg
+
+Code: [![Version](https://badge.fury.io/rb/huborg.png)](http://badge.fury.io/rb/huborg)
+
+Docs: [![Contribution Guidelines](http://img.shields.io/badge/CONTRIBUTING-Guidelines-blue.svg)](./CONTRIBUTING.md)
+[![Apache 2.0 License](http://img.shields.io/badge/APACHE2-license-blue.svg)](./LICENSE)
+
+Jump in: [![Slack Status](http://slack.samvera.org/badge.svg)](http://slack.samvera.org/)
+
+# What is huborg?
+
+The `huborg` gem is a set of Ruby classes that help script interactions with
+repositories within an organization (or organizations).
+
+## Product Owner & Maintenance
+
+The `huborg` gem is **NOT** a Core Component of the Samvera community. The documentation for
+what we mean by Core Component can be found
+[here](http://samvera.github.io/core_components.html#requirements-for-a-core-component).
+
+### Product Owner
+
+[jeremyf](https://github.com/jeremyf)
+
+# Help
+
+The Samvera community is here to help. Please see our [support guide](./SUPPORT.md).
+
+# Getting Started
+
+You'll need the `huborg` gem:
+
+* Install via `gem install huborg` **or**
+* Add it to your Gemfile: `gem "huborg"`
+
+## The Basics
+
+```ruby
+require 'huborg'
+
+# NOTE: You will need to include GITHUB_ACCESS_TOKEN in your ENV
+client = Huborg::Client.new(org_names: ["samvera", "samvera-labs"])
+# This command will push the given template to each repository in the above
+# organizations. By default it will not overwrite existing files.
+client.push_template!(
+  template: "/path/to/file/on/your/system",
+  filename: "relative/path/in/repository"
+)
+```
+
+The above will create a pull request against all repositories in
+"samvera" and "samvera-labs". That pull request will be to the file
+named `repository` (in the directory `relative/path/in`). The file's
+content will be from the file `/path/to/file/on/your/system`.
+
+## Further Refinements
+
+This example demonstrates the full parameter options:
+
+```ruby
+require 'huborg'
+require 'logger'
+
+client = Huborg::Client.new(
+    org_names: ["samvera", "samvera-labs"]),
+    logger: Logger.new(STDOUT),
+    github_access_token: "my-super-secret-token",
+    repository_pattern: %r{hyrax}i, # Limit to repositories with full name "hyrax"
+)
+client.push_template!(
+  template: "/path/to/file/on/your/system",
+  filename: "relative/path/in/repository",
+  overwrite: true
+)
+```
+
+## Prerequisites
+
+You'll want to have created a [Github OAuth Access Token](https://github.com/octokit/octokit.rb#oauth-access-tokens).
+
+## Hey, Where Are The Repository Tests?
+
+Great question. The product owner has chosen not to write the tests as the
+tests would be a preposterous amount of mocks and stubs. The product owner
+recommends that you, intrepid developer, create a Github organization of your
+own and add a few repositories to play against. That is what the product owner
+did, and will be how they test the `huborg` gem going forward.
+
+You, dear intrepid developer, can use the rake task `test:push_template` and
+look at your organization's repositories to see the pull request. The product
+owner used the following:
+
+```console
+$ export GITHUB_ACCESS_TOKEN=their-github-token
+$ export GITHUB_ORG_NAME=their-organization
+$ bundle exec rake test:push_template
+```
+
+## Todo
+
+- [ ] Add method to clone repositories
+- [ ] Add method to pull changes from upstream repositories
+- [ ] Add method to run stats against local repositories
+
+# Acknowledgments
+
+This software has been developed by and is brought to you by the Samvera community.  Learn more at the
+[Samvera website](http://samvera.org/).
+
+![Samvera Logo](https://wiki.lyrasis.org/download/thumbnails/87459292/samvera-fall-font2-200w.png?version=1&modificationDate=1498550535816&api=v2)

data/Rakefile

@@ -0,0 +1,16 @@
+require "bundler/gem_tasks"
+
+namespace :test do
+  desc "Push template to organization (set ENV[GITHUB_ACCESS_TOKEN] and ENV[GITHUB_ORG_NAME])"
+  task :push_template do
+    require 'huborg'
+    client = Huborg::Client.new(
+      github_access_token: ENV.fetch("GITHUB_ACCESS_TOKEN"),
+      org_names: ENV.fetch("GITHUB_ORG_NAME")
+    )
+    client.push_template!(
+      template: __FILE__,
+      filename: "disposable-#{Time.now.utc.to_s.gsub(/\D+/,'')}.rake"
+    )
+  end
+end

data/SUPPORT.md

@@ -0,0 +1,5 @@
+If you would like to report an issue, first search [the list of issues](https://github.com/samvera-labs/huborg/issues/) to see if someone else has already reported it, and then feel free to [create a new issue](https://github.com/samvera-labs/huborg/issues/new).
+
+If you have questions or need help, please email [the Samvera community tech list](https://groups.google.com/forum/#!forum/samvera-tech) or stop by the #dev channel in [the Samvera community Slack team](https://wiki.duraspace.org/pages/viewpage.action?pageId=87460391#Getintouch!-Slack).
+
+You can learn more about the various Samvera communication channels on the [Get in touch!](https://wiki.duraspace.org/pages/viewpage.action?pageId=87460391) wiki page.

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "huborg"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/huborg.gemspec

@@ -0,0 +1,27 @@
+require_relative 'lib/huborg/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "huborg"
+  spec.version       = Huborg::VERSION
+  spec.authors       = ["Jeremy Friesen"]
+  spec.email         = ["jeremy.n.friesen@gmail.com"]
+
+  spec.summary       = %q{Make changes to Organization Repositories en-masse.}
+  spec.description   = %q{Make changes to Organization Repositories en-masse.}
+  spec.homepage      = "https://github.com/samvera-labs/huborg/"
+  spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/samvera-labs/huborg/"
+  spec.metadata["changelog_uri"] = "https://github.com/samvera-labs/huborg/CHANGELOG.md"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+  spec.add_dependency "octokit", "~> 4.16"
+end

data/lib/huborg.rb

@@ -0,0 +1,182 @@
+require "huborg/version"
+require 'octokit'
+
+module Huborg
+  class Error < RuntimeError; end
+
+  # The class that interacts with organizational repositories
+  class Client
+
+    # Match all repositories
+    DEFAULT_REPOSITORY_PATTERN = %r{\A.*\Z}
+
+    # @param logger [Logger] used in logging output of processes
+    # @param github_access_token [String] used to connect to the Oktokit::Client.
+    #        The given token will need to have permission to interact with
+    #        repositories. Defaults to ENV["GITHUB_ACCESS_TOKEN"]
+    # @param org_names [Array<String>] used as the default list of Github organizations
+    #        in which we'll interact.
+    # @param repository_pattern [Regexp] limit the list of repositories to the given pattern; defaults to ALL
+    #
+    # @see https://github.com/octokit/octokit.rb#oauth-access-tokens
+    def initialize(logger: default_logger, github_access_token: default_access_token, org_names:, repository_pattern: DEFAULT_REPOSITORY_PATTERN)
+      @logger = logger
+      @client = Octokit::Client.new(access_token: github_access_token)
+      @org_names = Array(org_names)
+      @repository_pattern = repository_pattern
+    end
+    attr_reader :client, :logger, :org_names, :repository_pattern
+
+    private
+
+    def default_logger
+      require 'logger'
+      Logger.new(STDOUT)
+    end
+
+    def default_access_token
+      ENV.fetch('GITHUB_ACCESS_TOKEN')
+    rescue KeyError => e
+      $stderr.puts "You need to provide an OAuth Access Token.\nSee: https://github.com/octokit/octokit.rb#oauth-access-tokens"
+      raise e
+    end
+
+    public
+
+    # @api public
+    #
+    # Responsible for pushing the given template file to all of the
+    # organizations repositories. As we are pushing changes to
+    # repositories, this process will skip archived repositories.
+    #
+    # @note This skips archived repositories
+    #
+    # @param template [String] name of the template to push out to all
+    #        repositories
+    # @param filename [String] where in the repository should we write
+    #        the template. This is a relative pathname, each directory
+    #        and filename.
+    # @param overwrite [Boolean] because sometimes you shouldn't
+    #        overwrite what already exists. In the case of a LICENSE, we
+    #        would not want to do that. In the case of a .mailmap, we
+    #        would likely want to overwrite.
+    # @todo  Verify that the template exists
+    def push_template!(template:, filename:, overwrite: false)
+      each_repository do |repo|
+        push_template_to!(repo: repo, template: template, filename: filename, overwrite: overwrite)
+      end
+    end
+
+    # @api private
+    # @note API Private as this is not yet used.
+    #
+    # Fetch all of the repositories for the initialized :org_names that
+    # match the initialized :repository_pattern
+    #
+    # @yield if given, yield a Oktokit::Repository object for each
+    #        repository
+    # @yieldparam A raw Oktokit::Repository object
+    # @return [True]
+    def each_repository(&block)
+      # Collect all repositories
+      repos = []
+      org_names.each do |org_name|
+        org = client.org(org_name)
+        repos += fetch_rel_for(rel: :repos, org: org)
+      end
+
+      repos.each do |repo|
+        block.call(repo) if repository_pattern.match?(repo.full_name)
+      end
+      return true
+    end
+
+    private
+
+    # @note Due to an implementation detail in octokit.rb, refs sometimes
+    # need to be "heads/master" and "refs/heads/master" as detailed
+    # below
+    # @param repo [#full_name, #archived] Likely the result of Octokit::Client#org
+    # @param template [String] name of the template to push out to all
+    #        repositories
+    # @param filename [String] where in the repository should we write
+    #        the template. This is a relative pathname, each directory
+    #        and filename.
+    # @param overwrite [Boolean] because sometimes you shouldn't
+    #        overwrite what already exists. In the case of a LICENSE, we
+    #        would not want to do that. In the case of a .mailmap, we
+    #        would likely want to overwrite.
+    def push_template_to!(repo:, template:, filename:, overwrite: false)
+      return if repo.archived
+      # Note: Sometimes I'm using "heads/master" and other times I'm using
+      #       "refs/heads/master". There appears to be an inconsistency in
+      #       the implementation of octokit.
+      master = client.ref(repo.full_name, "heads/master")
+      copy_on_master = begin
+        # I have seen both a return value of nil or seen raised an Octokit::NotFound
+        # exception (one for a file at root, the other for a file in a non-existent
+        # directory)
+        client.contents(repo.full_name, path: filename)
+      rescue Octokit::NotFound
+        nil
+      end
+      commit_message = "Adding #{filename}\n\nThis was uploaded via automation."
+      logger.info("Creating pull request for #{filename} on #{repo.full_name}")
+      target_branch_name = "refs/heads/autoupdate-#{Time.now.utc.to_s.gsub(/\D+/,'')}"
+      if copy_on_master
+        return unless overwrite
+        branch = client.create_reference(repo.full_name, target_branch_name, master.object.sha)
+        client.update_contents(
+          repo.full_name,
+          filename,
+          commit_message,
+          copy_on_master.sha,
+          file: File.new(template, "r"),
+          branch: target_branch_name
+        )
+        client.create_pull_request(repo.full_name, "refs/heads/master", target_branch_name, commit_message)
+      else
+        branch = client.create_reference(repo.full_name, target_branch_name, master.object.sha)
+        client.create_contents(
+          repo.full_name,
+          filename,
+          commit_message,
+          file: File.new(template, "r"),
+          branch: target_branch_name
+        )
+        client.create_pull_request(repo.full_name, "refs/heads/master", target_branch_name, commit_message)
+      end
+    end
+
+    # Responsible for fetching an array of the given :rel
+    #
+    # @param rel [Symbol] The name of the related object(s) for the
+    #        given org
+    # @param org [Object] An Organization object (provided by Oktokit
+    #        object) from which this method fetchs the related :rel
+
+    # @return [Array<Object>]
+    def fetch_rel_for(rel:, org:)
+      # Build a list of repositories, note per Github's API, these are
+      # paginated.
+      logger.info "Fetching rels[#{rel.inspect}] for '#{org.login}' with pattern #{repository_pattern.inspect}"
+      source = org.rels[rel].get
+      rels = []
+      while source
+        rels += source.data
+        if source.rels[:next]
+          source = source.rels[:next].get
+        else
+          source = nil
+        end
+      end
+      rels
+      logger.info "Finished rels[#{rel.inspect}] for '#{org.login}' with pattern #{repository_pattern.inspect}"
+      if block_given?
+        rels
+      else
+        return rels
+      end
+    end
+  end
+end

data/lib/huborg/version.rb

@@ -0,0 +1,3 @@
+module Huborg
+  VERSION = "0.1.0"
+end

metadata

@@ -0,0 +1,72 @@
+--- !ruby/object:Gem::Specification
+name: huborg
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Jeremy Friesen
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2020-02-26 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: octokit
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '4.16'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '4.16'
+description: Make changes to Organization Repositories en-masse.
+email:
+- jeremy.n.friesen@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- Gemfile
+- LICENSE
+- README.md
+- Rakefile
+- SUPPORT.md
+- bin/console
+- bin/setup
+- huborg.gemspec
+- lib/huborg.rb
+- lib/huborg/version.rb
+homepage: https://github.com/samvera-labs/huborg/
+licenses: []
+metadata:
+  homepage_uri: https://github.com/samvera-labs/huborg/
+  source_code_uri: https://github.com/samvera-labs/huborg/
+  changelog_uri: https://github.com/samvera-labs/huborg/CHANGELOG.md
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.3.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.1.2
+signing_key: 
+specification_version: 4
+summary: Make changes to Organization Repositories en-masse.
+test_files: []