p-mongo-git 1.8.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: ac10e8c403b0765e105cd889b2b74d8001067439e09108d92856501ce6dc0453
+  data.tar.gz: 41f289207c76f26208fb72d9a39e958e32d086c65560ef81f7536d841c221943
+SHA512:
+  metadata.gz: 4476ee5c0f716c96f591554933097f7aada9b1ed074b7a26d36c064fec2ae09e436bf3d76366e5fc2c3428349c45c1ac9d42ece1288b5fb8a3756b60a2aca626
+  data.tar.gz: 2958b59196610800b7c575bfde6fded147ff55eea08f6064bb6d581f782b6db7732f3cce66e8ca2fde74d708a4db19232610f53f717a4849a00238251acb54d6

data/.github/stale.yml

@@ -0,0 +1,25 @@
+# Probot: Stale
+# https://github.com/probot/stale
+
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 60
+
+# Number of days of inactivity before a stale issue is closed
+# Set to false to disable. If disabled, issues still need to be closed
+# manually, but will remain marked as stale.
+daysUntilClose: false
+
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+
+# Label to use when marking an issue as stale
+staleLabel: stale
+
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  A friendly reminder that this issue had no activity for 60 days.
+
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

data/.github/workflows/continuous_integration.yml

@@ -0,0 +1,45 @@
+name: CI
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    branches: [master]
+
+jobs:
+  continuous_integration_build:
+    continue-on-error: true
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby: [2.3, 2.7]
+        operating-system: [ubuntu-latest]
+        include:
+          - ruby: head
+            operating-system: ubuntu-latest
+          - ruby: truffleruby-head
+            operating-system: ubuntu-latest
+          - ruby: 2.7
+            operating-system: windows-latest
+          - ruby: jruby-head
+            operating-system: windows-latest
+
+    name: Ruby ${{ matrix.ruby }} on ${{ matrix.operating-system }}
+
+    runs-on: ${{ matrix.operating-system }}
+
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v2
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+
+      - name: Run Build
+        run: bundle exec rake default
+
+      - name: Test Gem
+        run: bundle exec rake test:gem

data/.gitignore

@@ -0,0 +1,10 @@
+*.gem
+*.kpf
+*.sw?
+.DS_Store
+coverage
+doc
+.yardoc
+pkg
+rdoc
+Gemfile.lock

data/.yardopts

@@ -0,0 +1,11 @@
+--default-return=''
+--hide-void-return
+--markup-provider=redcarpet
+--markup=markdown
+--fail-on-warning
+-
+README.md
+CHANGELOG.md
+CONTRIBUTING.md
+RELEASING.md
+MAINTAINERS.md

data/CHANGELOG.md

@@ -0,0 +1,119 @@
+<!--
+# @markup markdown
+# @title Change Log
+-->
+
+# Change Log
+
+## 1.8.1
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.8.1
+
+## 1.8.0
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.8.0
+
+## 1.7.0
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.7.0
+
+## 1.6.0
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.6.0
+
+## 1.6.0.pre1
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.6.0.pre1
+
+## 1.5.0
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.5.0
+
+## 1.4.0
+
+See https://github.com/ruby-git/ruby-git/releases/tag/v1.4.0
+
+## 1.3.0
+
+ * Dropping Ruby 1.8.x support
+
+## 1.2.10
+
+ * Adding Git::Diff.name_status
+ * Checking and fixing encoding on commands output to prevent encoding errors afterwards
+
+## 1.2.9
+
+* Adding Git.configure (to configure the git env)
+* Adding Git.ls_remote [Git.ls_remote(repo_path_or_url='.')]
+* Adding Git.describe [repo.describe(objectish, opts)]
+* Adding Git.show [repo.show(objectish=nil, path=nil)]
+* Fixing Git::Diff to support default references (implicit references)
+* Fixing Git::Diff to support diff over git .patch files
+* Fixing Git.checkout when using :new_branch opt
+* Fixing Git::Object::Commit to preserve its sha after fetching metadata
+* Fixing Git.is_remote_branch? to actually check against remote branches
+* Improvements over how ENV variables are modified
+* Improving thrade safety (using --git-dir and --work-tree git opts)
+* Improving Git::Object::Tag. Adding annotated?, tagger and message
+* Supporting a submodule path as a valid repo
+* Git.checkout - supporting -f and -b
+* Git.clone - supporting --branch
+* Git.fetch - supporting --prune
+* Git.tag - supporting
+
+## 1.2.8
+
+* Keeping the old escape format for windows users
+* revparse: Supporting ref names containing SHA like substrings (40-hex strings)
+* Fix warnings on Ruby 2.1.2
+
+## 1.2.7
+
+* Fixing mesages encoding
+* Fixing -f flag in git push
+* Fixing log parser for multiline messages
+* Supporting object references on Git.add_tag
+* Including dotfiles on Git.status
+* Git.fetch - supporting --tags
+* Git.clean - supporting -x
+* Git.add_tag options - supporting -a, -m and -s
+* Added Git.delete_tag
+
+## 1.2.6
+
+* Ruby 1.9.X/2.0 fully supported
+* JRuby 1.8/1.9 support
+* Rubinius support
+* Git.clone - supporting --recursive and --config
+* Git.log - supporting last and [] over the results
+* Git.add_remote - supporting -f and -t
+* Git.add - supporting --fore
+* Git.init - supporting --bare
+* Git.commit - supporting --all and --amend
+* Added Git.remote_remote, Git.revert and Git.clean
+* Added Bundler to the formula
+* Travis configuration
+* Licence included with the gem
+
+## 1.0.4
+
+* added camping/gitweb.rb frontend
+* added a number of speed-ups
+
+## 1.0.3
+
+* Sped up most of the operations
+* Added some predicate functions (commit?, tree?, etc)
+* Added a number of lower level operations (read-tree, write-tree, checkout-index, etc)
+* Fixed a bug with using bare repositories
+* Updated a good amount of the documentation
+
+## 1.0.2
+
+* Added methods to the git objects that might be helpful
+
+## 1.0.1
+
+* Initial version
+

data/CONTRIBUTING.md

@@ -0,0 +1,151 @@
+<!--
+# @markup markdown
+# @title How To Contribute
+-->
+
+# Contributing to ruby-git
+
+Thank you for your interest in contributing to the ruby-git project.
+
+This document gives the guidelines for contributing to the ruby-git project.
+These guidelines may not fit every situation.  When contributing use your best
+judgement.
+
+Propose changes to these guidelines with a pull request.
+
+## How to contribute
+
+You can contribute in two ways:
+
+1. [Report an issue or make a feature request](#how-to-report-an-issue-or-make-a-feature-request)
+2. [Submit a code or documentation change](#how-to-submit-a-code-or-documentation-change)
+
+## How to report an issue or make a feature request
+
+ruby-git utilizes [GitHub Issues](https://help.github.com/en/github/managing-your-work-on-github/about-issues)
+for issue tracking and feature requests.
+
+Report an issue or feature request by [creating a ruby-git Github issue](https://github.com/ruby-git/ruby-git/issues/new).
+Fill in the template to describe the issue or feature request the best you can.
+
+## How to submit a code or documentation change
+
+There is three step process for code or documentation changes:
+
+1. [Commit your changes to a fork of ruby-git](#commit-changes-to-a-fork-of-ruby-git)
+2. [Create a pull request](#create-a-pull-request)
+3. [Get your pull request reviewed](#get-your-pull-request-reviewed)
+
+### Commit changes to a fork of ruby-git
+
+Make your changes in a fork of the ruby-git repository.
+
+Each commit must include a [DCO sign-off](#developer-certificate-of-origin-dco)
+by adding the line `Signed-off-by: Name <email>` to the end of the commit
+message.
+
+### Create a pull request
+
+See [this article](https://help.github.com/articles/about-pull-requests/) if you
+are not familiar with GitHub Pull Requests.
+
+Follow the instructions in the pull request template.
+
+### Get your pull request reviewed
+
+Code review takes place in a GitHub pull request using the [the Github pull request review feature](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews).
+
+Once your pull request is ready for review, request a review from at least one
+[maintainer](MAINTAINERS.md) and any number of other contributors.
+
+During the review process, you may need to make additional commits which would
+need to be squashed.  It may also be necessary to rebase to master again if other
+changes are merged before your PR.
+
+At least one approval is required from a project maintainer before your pull
+request can be merged.  The maintainer is responsible for ensuring that the pull
+request meets [the project's coding standards](#coding-standards).
+
+## Coding standards
+
+In order to ensure high quality, all pull requests must meet these requirements:
+
+### 1 PR = 1 Commit
+  * All commits for a PR must be squashed into one commit
+  * To avoid an extra merge commit, the PR must be able to be merged as [a fast forward merge](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)
+  * The easiest way to ensure a fast forward merge is to rebase your local branch
+    to the ruby-git master branch
+
+### Unit tests
+  * All changes must be accompanied by new or modified unit tests
+  * The entire test suite must pass when `bundle exec rake default` is run from the
+    project's local working copy.
+
+### Continuous integration
+  * All tests must pass in the project's [GitHub Continuous Integration build](https://github.com/ruby-git/ruby-git/actions?query=workflow%3ACI)
+    before the pull request will be merged.
+  * The [Continuous Integration workflow](https://github.com/ruby-git/ruby-git/blob/master/.github/workflows/continuous_integration.yml)
+    runs both `bundle exec rake default` and `bundle exec rake test:gem` from the project's [Rakefile](https://github.com/ruby-git/ruby-git/blob/master/Rakefile).
+
+### Documentation
+  * New and updated public methods must have [YARD](https://yardoc.org/)
+    documentation added to them
+  * New and updated public facing features should be documented in the project's
+    [README.md](README.md)
+
+### Licensing sign-off
+  * Each commit must contain [the DCO sign-off](#developer-certificate-of-origin-dco)
+    in the form:  `Signed-off-by: Name <email>`
+
+## Licensing
+
+ruby-git uses [the MIT license](https://choosealicense.com/licenses/mit/) as
+declared in the [LICENSE](LICENSE) file.
+
+Licensing is very important to open source projects. It helps ensure the
+software continues to be available under the terms that the author desired.
+
+### Developer Certificate of Origin (DCO)
+
+This project requires that authors have permission to submit their contributions
+under the MIT license. To make a good faith effort to ensure this, ruby-git
+requires the [Developer Certificate of Origin (DCO)](https://elinux.org/Developer_Certificate_Of_Origin)
+process be followed.
+
+This process requires that each commit include a `Signed-off-by` line that
+indicates the author accepts the DCO.  Here is an example DCO sign-off line:
+
+```
+Signed-off-by: John Doe <john.doe@hisdomain.com>
+```
+
+The full text of the DCO version 1.1 is below or at <http://developercertificate.org/>.
+
+```
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the
+    best of my knowledge, is covered under an appropriate open
+    source license and I have the right under that license to
+    submit that work with modifications, whether created in whole
+    or in part by me, under the same open source license (unless
+    I am permitted to submit under a different license), as
+    Indicated in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including
+    all personal information I submit with it, including my
+    sign-off) is maintained indefinitely and may be redistributed
+    consistent with this project or the open source license(s)
+    involved.
+```

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+gemspec :name => 'git'
+

data/ISSUE_TEMPLATE.md

@@ -0,0 +1,15 @@
+### Subject of the issue
+Describe your issue here.
+
+### Your environment
+* version of git and ruby-git
+* version of ruby
+
+### Steps to reproduce
+Tell us how to reproduce this issue. 
+
+### Expected behaviour
+What did you expect to happen?
+
+### Actual behaviour
+What actually happened?

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2008 Scott Chacon
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/MAINTAINERS.md

@@ -0,0 +1,14 @@
+<!--
+# @markup markdown
+# @title Maintainers
+-->
+
+# Maintainers
+
+When making changes in this repository, one of the maintainers below must review and approve your pull request.
+
+### Maintainers
+
+* [Per Lundberg](https://github.com/perlun)
+* [Vern Burton](https://github.com/tarcinil)
+* [James Couball](https://github.com/jcouball)

data/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+### Your checklist for this pull request
+🚨Please review the [guidelines for contributing](https://github.com/ruby-git/ruby-git/blob/master/CONTRIBUTING.md) to this repository.
+
+- [ ] Ensure all commits include DCO sign-off.
+- [ ] Ensure that your contributions pass unit testing.
+- [ ] Ensure that your contributions contain documentation if applicable.
+
+### Description
+Please describe your pull request.