git 1.19.1 → 5.5.0

data/Dockerfile.changelog-rs

@@ -1,12 +0,0 @@
-FROM rust
-
-# Build the docker image (from this project's root directory):
-# docker build --file Dockerfile.changelog-rs --tag changelog-rs .
-#
-# Use this image to output a changelog (from this project's root directory):
-# docker run --rm --volume "$PWD:/worktree" changelog-rs v1.9.1 v1.10.0
-
-RUN cargo install changelog-rs
-WORKDIR /worktree
-
-ENTRYPOINT ["/usr/local/cargo/bin/changelog-rs", "/worktree"]

data/Gemfile

@@ -1,5 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-gemspec name: 'git'

data/ISSUE_TEMPLATE.md

@@ -1,15 +0,0 @@
-### 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/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +0,0 @@
-### 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.

data/RELEASING.md

@@ -1,70 +0,0 @@
-<!--
-# @markup markdown
-# @title Releasing
--->
-
-# How to release a new git.gem
-
-Releasing a new version of the `git` gem requires these steps:
-
-- [How to release a new git.gem](#how-to-release-a-new-gitgem)
-  - [Install Prerequisites](#install-prerequisites)
-  - [Prepare the Release](#prepare-the-release)
-  - [Review and Merge the Release](#review-and-merge-the-release)
-  - [Build and Release the Gem](#build-and-release-the-gem)
-
-These instructions use an example where:
-
-- The default branch is `master`
-- The current release version is `1.5.0`
-- You want to create a new *minor* release, `1.6.0`
-
-## Install Prerequisites
-
-The following tools need to be installed in order to create the release:
-
-- [git](https://git-scm.com) is used to interact with the local and remote repositories
-- [gh](https://cli.github.com) is used to create the release and PR in GitHub
-- [Docker](https://www.docker.com) is used to run the script to create the release notes
-
-On a Mac, these tools can be installed using [brew](https://brew.sh):
-
-```shell
-$ brew install git
-...
-$ brew install gh
-...
-$ brew install --cask docker
-...
-$
-```
-
-## Prepare the Release
-
-Bump the version, create release notes, tag the release and create a GitHub release and PR which can be used to review the release.
-
-Steps:
-
-- Check out the code with `git clone https://github.com/ruby-git/ruby-git ruby-git-v1.6.0 && cd ruby-git-v1.6.0`
-- Install development dependencies using bundle `bundle install`
-- Based upon the nature of the changes, decide on the type of release: `major`, `minor`, or `patch` (in this example we will use `minor`)
-- Run the release script `bundle exec create-github-release minor`
-
-## Review and Merge the Release
-
-Have the release PR approved and merge the changes into the `master` branch.
-
-**IMPORTANT** DO NOT merge to the `master` branch using the GitHub UI. Instead use the instructions below.
-
-Steps:
-
-- Get the release PR reviewed and approved in GitHub
-- Merge the changes with the command `git checkout master && git merge --ff-only v1.6.0 && git push`
-
-## Build and Release the Gem
-
-Build the gem and publish it to [rubygems.org](https://rubygems.org/gems/git)
-
-Steps:
-
-- Build and release the gem using rake `bundle exec rake release`

data/Rakefile

@@ -1,60 +0,0 @@
-require 'bundler/gem_tasks'
-require 'English'
-
-require 'git/version'
-
-default_tasks = []
-
-desc 'Run Unit Tests'
-task :test do
-  sh 'ruby bin/test'
-
-  # You can run individual test files (or multiple files) from the command
-  # line with:
-  #
-  # $ bin/test tests/units/test_archive.rb
-  #
-  # $ bin/test tests/units/test_archive.rb tests/units/test_object.rb
-end
-default_tasks << :test
-
-unless RUBY_PLATFORM == 'java' || RUBY_ENGINE == 'truffleruby'
-  #
-  # YARD documentation for this project can NOT be built with JRuby.
-  # This project uses the redcarpet gem which can not be installed on JRuby.
-  #
-  require 'yard'
-  YARD::Rake::YardocTask.new
-  CLEAN << '.yardoc'
-  CLEAN << 'doc'
-  default_tasks << :yard
-
-  require 'yardstick/rake/verify'
-  Yardstick::Rake::Verify.new(:'yardstick:coverage') do |t|
-    t.threshold = 50
-    t.require_exact_threshold = false
-  end
-  default_tasks << :'yardstick:coverage'
-
-  desc 'Run yardstick to check yard docs'
-  task :yardstick do
-    sh "yardstick 'lib/**/*.rb'"
-  end
-  # Do not include yardstick as a default task for now since there are too many
-  # warnings.  Will work to get the warnings down before re-enabling it.
-  #
-  # default_tasks << :yardstick
-end
-
-default_tasks << :build
-
-task default: default_tasks
-
-desc 'Build and install the git gem and run a sanity check'
-task :'test:gem' => :install do
-  output = `ruby -e "require 'git'; g = Git.open('.'); puts g.log.size"`.chomp
-  raise 'Gem test failed' unless $CHILD_STATUS.success?
-  raise 'Expected gem test to return an integer' unless output =~ /^\d+$/
-
-  puts 'Gem Test Succeeded'
-end

data/lib/git/base/factory.rb

@@ -1,99 +0,0 @@
-module Git
-
-  class Base
-
-    module Factory
-      # @return [Git::Branch] an object for branch_name
-      def branch(branch_name = self.current_branch)
-        Git::Branch.new(self, branch_name)
-      end
-
-      # @return [Git::Branches] a collection of all the branches in the repository.
-      #   Each branch is represented as a {Git::Branch}.
-      def branches
-        Git::Branches.new(self)
-      end
-
-      # returns a Git::Worktree object for dir, commitish
-      def worktree(dir, commitish = nil)
-        Git::Worktree.new(self, dir, commitish)
-      end
-
-      # returns a Git::worktrees object of all the Git::Worktrees
-      # objects for this repo
-      def worktrees
-        Git::Worktrees.new(self)
-      end
-
-      # @return [Git::Object::Commit] a commit object
-      def commit_tree(tree = nil, opts = {})
-        Git::Object::Commit.new(self, self.lib.commit_tree(tree, opts))
-      end
-
-      # @return [Git::Diff] a Git::Diff object
-      def diff(objectish = 'HEAD', obj2 = nil)
-        Git::Diff.new(self, objectish, obj2)
-      end
-
-      # @return [Git::Object] a Git object
-      def gblob(objectish)
-        Git::Object.new(self, objectish, 'blob')
-      end
-
-      # @return [Git::Object] a Git object
-      def gcommit(objectish)
-        Git::Object.new(self, objectish, 'commit')
-      end
-
-      # @return [Git::Object] a Git object
-      def gtree(objectish)
-        Git::Object.new(self, objectish, 'tree')
-      end
-
-      # @return [Git::Log] a log with the specified number of commits
-      def log(count = 30)
-        Git::Log.new(self, count)
-      end
-
-      # returns a Git::Object of the appropriate type
-      # you can also call @git.gtree('tree'), but that's
-      # just for readability.  If you call @git.gtree('HEAD') it will
-      # still return a Git::Object::Commit object.
-      #
-      # object calls a factory method that will run a rev-parse
-      # on the objectish and determine the type of the object and return
-      # an appropriate object for that type
-      #
-      # @return [Git::Object] an instance of the appropriate type of Git::Object
-      def object(objectish)
-        Git::Object.new(self, objectish)
-      end
-
-      # @return [Git::Remote] a remote of the specified name
-      def remote(remote_name = 'origin')
-        Git::Remote.new(self, remote_name)
-      end
-
-      # @return [Git::Status] a status object
-      def status
-        Git::Status.new(self)
-      end
-
-      # @return [Git::Object::Tag] a tag object
-      def tag(tag_name)
-        Git::Object.new(self, tag_name, 'tag', true)
-      end
-
-      # Find as good common ancestors as possible for a merge
-      # example: g.merge_base('master', 'some_branch', 'some_sha', octopus: true)
-      #
-      # @return [Array<Git::Object::Commit>] a collection of common ancestors
-      def merge_base(*args)
-        shas = self.lib.merge_base(*args)
-        shas.map { |sha| gcommit(sha) }
-      end
-    end
-
-  end
-
-end