git 3.0.1 → 3.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ac9ecaecd0650db542fe2d5efbddea96b362130fb8c34aca2e4ee19ded74c261
-  data.tar.gz: ca88749488ed11bbd9bd13444e658e1c3dbf02b6e453327691ddbc9f8df949a0
+  metadata.gz: 511ce73ebd49de3ef2985b430f6aef69828bef58f15f4272ff835328b1275fc3
+  data.tar.gz: a223cc03fef4b9968b5ff30ba2521ab841e9c4e15e311dbb7d94bec16b466373
 SHA512:
-  metadata.gz: f46b58cc1faade68c215b482e1907107fa61b705bd4f70259d8b271c77c2d9743506cdec921c1f3c27006d3483bc0aa0827755e1e1c82f3c20ecb62c1496c71a
-  data.tar.gz: fd8d45a2828536ef4da8e07917c309b12d9f0b3d4d7431c0ffadab6b0e83d3ad868cebb40f48435d72924f65d7bcf516aea433755ddfed0c084f8df6f31e3dbe
+  metadata.gz: 8bb93e9a89b396c30ed1ce535baa972a9d52a9c8afe63cbdee55520881cb9d0921eb85cea447779ee78469812a3b939de8a9a47a10996f47502e8bf1bd9cdb05
+  data.tar.gz: d9b075c42d95fd121986e3a79fc87acbd634aefa06228a139104ac189c7258351ee88a4607638184d92f03668d67253412b39d50a9a8994c63943b38353d2f8a

data/.commitlintrc.yml

@@ -0,0 +1,38 @@
+---
+extends: '@commitlint/config-conventional'
+
+rules:
+  # See: https://commitlint.js.org/reference/rules.html
+  #
+  # Rules are made up by a name and a configuration array. The configuration
+  # array contains:
+  #
+  # * Severity [0..2]: 0 disable rule, 1 warning if violated, or 2 error if
+  #   violated
+  # * Applicability [always|never]: never inverts the rule
+  # * Value: value to use for this rule (if applicable)
+  #
+  # Run `npx commitlint --print-config` to see the current setting for all
+  # rules.
+  #
+  header-max-length:      [2, always, 100]        # Header can not exceed 100 chars
+
+  type-case:              [2, always, lower-case] # Type must be lower case
+  type-empty:             [2, never]              # Type must not be empty
+
+  # Supported conventional commit types
+  type-enum:              [2, always, [build, ci, chore, docs, feat, fix, perf, refactor, revert, style, test]]
+
+  scope-case:             [2, always, lower-case] # Scope must be lower case
+
+  # Error if subject is one of these cases (encourages lower-case)
+  subject-case:           [2, never, [sentence-case, start-case, pascal-case, upper-case]]
+  subject-empty:          [2, never]              # Subject must not be empty
+  subject-full-stop:      [2, never, "."]         # Subject must not end with a period
+
+  body-leading-blank:     [2, always]             # Body must have a blank line before it
+  body-max-line-length:   [2, always, 100]        # Body lines can not exceed 100 chars
+
+  footer-leading-blank:   [2, always]             # Footer must have a blank line before it
+  footer-max-line-length: [2, always, 100]        # Footer lines can not exceed 100 chars
+  

data/.github/workflows/continuous_integration.yml

@@ -1,15 +1,19 @@
 name: CI
 
 on:
-  push:
-    branches: [master,v1]
   pull_request:
-    branches: [master,v1]
+    branches: [master]
   workflow_dispatch:
 
 jobs:
   build:
     name: Ruby ${{ matrix.ruby }} on ${{ matrix.operating-system }}
+
+    # Skip this job if triggered by a release PR
+    if: >-
+      github.event_name == 'workflow_dispatch' ||
+      (github.event_name == 'pull_request' && !startsWith(github.event.pull_request.head.ref, 'release-please--'))
+
     runs-on: ${{ matrix.operating-system }}
     continue-on-error: ${{ matrix.experimental == 'Yes' }}
     env: { JAVA_OPTS: -Djdk.io.File.enableADS=true }

data/.github/workflows/enforce_conventional_commits.yml

@@ -0,0 +1,28 @@
+---
+name: Conventional Commits
+
+permissions:
+  contents: read
+
+on:
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  commit-lint:
+    name: Verify Conventional Commits
+
+    # Skip this job if this is a release PR
+    if: (github.event_name == 'pull_request' && !startsWith(github.event.pull_request.head.ref, 'release-please--'))
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with: { fetch-depth: 0 }
+
+      - name: Check Commit Messages
+        uses: wagoid/commitlint-github-action@v6
+        with: { configFile: .commitlintrc.yml }

data/.github/workflows/experimental_continuous_integration.yml

@@ -2,12 +2,19 @@ name: CI Experimental
 
 on:
   push:
-    branches: [master,v1]
+    branches: [master]
+
   workflow_dispatch:
 
 jobs:
   build:
     name: Ruby ${{ matrix.ruby }} on ${{ matrix.operating-system }}
+
+    # Skip this job if triggered by pushing a release commit
+    if: >-
+      github.event_name == 'workflow_dispatch' ||
+      (github.event_name == 'push' && !startsWith(github.event.head_commit.message, 'chore: release '))
+
     runs-on: ${{ matrix.operating-system }}
     continue-on-error: true
     env: { JAVA_OPTS: -Djdk.io.File.enableADS=true }

data/.github/workflows/release.yml

@@ -0,0 +1,52 @@
+---
+name: Release Gem
+
+description: |
+  This workflow creates a new release on GitHub and publishes the gem to
+  RubyGems.org.
+
+  The workflow uses the `googleapis/release-please-action` to handle the
+  release creation process and the `rubygems/release-gem` action to publish
+  the gem to rubygems.org
+
+on:
+  push:
+    branches: ["master"]
+
+  workflow_dispatch:
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+
+    environment:
+      name: RubyGems
+      url: https://rubygems.org/gems/git
+
+    permissions:
+      contents: write
+      pull-requests: write
+      id-token: write
+
+    steps:
+      - name: Checkout project
+        uses: actions/checkout@v4
+
+      - name: Create release
+        uses: googleapis/release-please-action@v4
+        id: release
+        with:
+          token: ${{ secrets.AUTO_RELEASE_TOKEN }}
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+
+      - name: Setup ruby
+        uses: ruby/setup-ruby@v1
+        if: ${{ steps.release.outputs.release_created }}
+        with:
+          bundler-cache: true
+          ruby-version: ruby
+
+      - name: Push to RubyGems.org
+        uses: rubygems/release-gem@v1
+        if: ${{ steps.release.outputs.release_created }}

data/.gitignore

@@ -8,3 +8,5 @@ doc
 pkg
 rdoc
 Gemfile.lock
+node_modules
+package-lock.json

data/.husky/commit-msg

@@ -0,0 +1 @@
+npx --no-install commitlint --edit "$1"

data/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "3.1.0"
+}

data/.yardopts

@@ -7,5 +7,4 @@
 README.md
 CHANGELOG.md
 CONTRIBUTING.md
-RELEASING.md
 MAINTAINERS.md

data/CHANGELOG.md

@@ -5,6 +5,34 @@
 
 # Change Log
 
+## [3.1.0](https://github.com/ruby-git/ruby-git/compare/v3.0.2...v3.1.0) (2025-05-18)
+
+
+### Features
+
+* Make Git::Log support the git log --merges option ([df3b07d](https://github.com/ruby-git/ruby-git/commit/df3b07d0f14d79c6c77edc04550c1ad0207c920a))
+
+
+### Other Changes
+
+* Announce and document guidelines for using Conventional Commits ([a832259](https://github.com/ruby-git/ruby-git/commit/a832259314aa9c8bdd7719e50d425917df1df831))
+* Skip continuous integration workflow for release PRs ([f647a18](https://github.com/ruby-git/ruby-git/commit/f647a18c8a3ae78f49c8cd485db4660aa10a92fc))
+* Skip the experiemental build workflow if a release commit is pushed to master ([3dab0b3](https://github.com/ruby-git/ruby-git/commit/3dab0b34e41393a43437c53a53b96895fd3d2cc5))
+
+## [3.0.2](https://github.com/ruby-git/ruby-git/compare/v3.0.1...v3.0.2) (2025-05-15)
+
+
+### Bug Fixes
+
+* Trigger the release workflow on a change to 'master' insetad of 'main' ([c8611f1](https://github.com/ruby-git/ruby-git/commit/c8611f1e68e73825fd16bd475752a40b0088d4ae))
+
+
+### Other Changes
+
+* Automate continuous delivery workflow ([06480e6](https://github.com/ruby-git/ruby-git/commit/06480e65e2441348230ef10e05cc1c563d0e7ea8))
+* Enforce conventional commit messages with a GitHub action ([1da4c44](https://github.com/ruby-git/ruby-git/commit/1da4c44620a3264d4e837befd3f40416c5d8f1d8))
+* Enforce conventional commit messages with husky and commitlint ([7ebe0f8](https://github.com/ruby-git/ruby-git/commit/7ebe0f8626ecb2f0da023b903b82f7332d8afaf6))
+
 ## v3.0.1 (2025-05-14)
 
 [Full Changelog](https://github.com/ruby-git/ruby-git/compare/v3.0.0..v3.0.1)

data/CONTRIBUTING.md

@@ -5,28 +5,30 @@
 
 # Contributing to the git gem
 
-* [Summary](#summary)
-* [How to contribute](#how-to-contribute)
-* [How to report an issue or request a feature](#how-to-report-an-issue-or-request-a-feature)
-* [How to submit a code or documentation change](#how-to-submit-a-code-or-documentation-change)
-  * [Commit your changes to a fork of `ruby-git`](#commit-your-changes-to-a-fork-of-ruby-git)
-  * [Create a pull request](#create-a-pull-request)
-  * [Get your pull request reviewed](#get-your-pull-request-reviewed)
-* [Design philosophy](#design-philosophy)
-  * [Direct mapping to git commands](#direct-mapping-to-git-commands)
-  * [Parameter naming](#parameter-naming)
-  * [Output processing](#output-processing)
-* [Coding standards](#coding-standards)
-  * [1 PR = 1 Commit](#1-pr--1-commit)
-  * [Unit tests](#unit-tests)
-  * [Continuous integration](#continuous-integration)
-  * [Documentation](#documentation)
-* [Building a specific version of the Git command-line](#building-a-specific-version-of-the-git-command-line)
-  * [Install pre-requisites](#install-pre-requisites)
-  * [Obtain Git source code](#obtain-git-source-code)
-  * [Build git](#build-git)
-  * [Use the new Git version](#use-the-new-git-version)
-* [Licensing](#licensing)
+- [Summary](#summary)
+- [How to contribute](#how-to-contribute)
+- [How to report an issue or request a feature](#how-to-report-an-issue-or-request-a-feature)
+- [How to submit a code or documentation change](#how-to-submit-a-code-or-documentation-change)
+  - [Commit your changes to a fork of `ruby-git`](#commit-your-changes-to-a-fork-of-ruby-git)
+  - [Create a pull request](#create-a-pull-request)
+  - [Get your pull request reviewed](#get-your-pull-request-reviewed)
+- [Design philosophy](#design-philosophy)
+  - [Direct mapping to git commands](#direct-mapping-to-git-commands)
+  - [Parameter naming](#parameter-naming)
+  - [Output processing](#output-processing)
+- [Coding standards](#coding-standards)
+  - [Commit message guidelines](#commit-message-guidelines)
+    - [What does this mean for contributors?](#what-does-this-mean-for-contributors)
+    - [What to know about Conventional Commits](#what-to-know-about-conventional-commits)
+  - [Unit tests](#unit-tests)
+  - [Continuous integration](#continuous-integration)
+  - [Documentation](#documentation)
+- [Building a specific version of the Git command-line](#building-a-specific-version-of-the-git-command-line)
+  - [Install pre-requisites](#install-pre-requisites)
+  - [Obtain Git source code](#obtain-git-source-code)
+  - [Build git](#build-git)
+  - [Use the new Git version](#use-the-new-git-version)
+- [Licensing](#licensing)
 
 ## Summary
 
@@ -63,7 +65,8 @@ thoroughly as possible to describe the issue or feature request.
 There is a three-step process for submitting code or documentation changes:
 
 1. [Commit your changes to a fork of
-   `ruby-git`](#commit-your-changes-to-a-fork-of-ruby-git)
+   `ruby-git`](#commit-your-changes-to-a-fork-of-ruby-git) using [Conventional
+   Commits](#commit-message-guidelines)
 2. [Create a pull request](#create-a-pull-request)
 3. [Get your pull request reviewed](#get-your-pull-request-reviewed)
 
@@ -153,18 +156,88 @@ behavior.
 To ensure high-quality contributions, all pull requests must meet the following
 requirements:
 
-### 1 PR = 1 Commit
+### Commit message guidelines
 
-* All commits for a PR must be squashed into a single 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.
+To enhance our development workflow, enable automated changelog generation, and pave
+the way for Continuous Delivery, the `ruby-git` project has adopted the [Conventional
+Commits standard](https://www.conventionalcommits.org/en/v1.0.0/) for all commit
+messages.
+
+This structured approach to commit messages allows us to:
+
+- **Automate versioning and releases:** Tools can now automatically determine the
+  semantic version bump (patch, minor, major) based on the types of commits merged.
+- **Generate accurate changelogs:** We can automatically create and update a
+  `CHANGELOG.md` file, providing a clear history of changes for users and
+  contributors.
+- **Improve commit history readability:** A standardized format makes it easier for
+  everyone to understand the nature of changes at a glance.
+
+#### What does this mean for contributors?
+
+Going forward, all commits to this repository **MUST** adhere to the [Conventional
+Commits standard](https://www.conventionalcommits.org/en/v1.0.0/). Commits not
+adhering to this standard will cause the CI build to fail. PRs will not be merged if
+they include non-conventional commits.
+
+A git pre-commit hook may be installed to validate your conventional commit messages
+before pushing them to GitHub by running `bin/setup` in the project root.
+
+#### What to know about Conventional Commits
+
+The simplist conventional commit is in the form `type: description` where `type`
+indicates the type of change and `description` is your usual commit message (with
+some limitations).
+
+- Types include: `feat`, `fix`, `docs`, `test`, `refactor`, and `chore`. See the full
+  list of types supported in [.commitlintrc.yml](.commitlintrc.yml).
+- The description must (1) not start with an upper case letter, (2) be no more than
+  100 characters, and (3) not end with punctuation.
+
+Examples of valid commits:
+
+- `feat: add the --merges option to Git::Lib.log`
+- `fix: exception thrown by Git::Lib.log when repo has no commits`
+- `docs: add conventional commit announcement to README.md`
+
+Commits that include breaking changes must include an exclaimation mark before the
+colon:
+
+- `feat!: removed Git::Base.commit_force`
+
+The commit messages will drive how the version is incremented for each release:
+
+- a release containing a **breaking change** will do a **major** version increment
+- a release containing a **new feature** will do a **minor** increment
+- a release containing **neither a breaking change nor a new feature** will do a
+  **patch** version increment
+
+The full conventional commit format is:
+
+```text
+<type>[optional scope][!]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+- `optional body` may include multiple lines of descriptive text limited to 100 chars
+  each
+- `optional footers` only uses `BREAKING CHANGE: <description>` where description
+  should describe the nature of the backward incompatibility.
+
+Use of the `BREAKING CHANGE:` footer flags a backward incompatible change even if it
+is not flagged with an exclaimation mark after the `type`. Other footers are allowed
+by not acted upon.
+
+See [the Conventional Commits
+specification](https://www.conventionalcommits.org/en/v1.0.0/) for more details.
 
 ### 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
+- 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.
 
 While working on specific features, you can run individual test files or a group of

data/README.md

@@ -9,17 +9,34 @@
 [![Documentation](https://img.shields.io/badge/Documentation-Latest-green)](https://rubydoc.info/gems/git/)
 [![Change Log](https://img.shields.io/badge/CHANGELOG-Latest-green)](https://rubydoc.info/gems/git/file/CHANGELOG.md)
 [![Build Status](https://github.com/ruby-git/ruby-git/workflows/CI/badge.svg?branch=master)](https://github.com/ruby-git/ruby-git/actions?query=workflow%3ACI)
-[![Code Climate](https://codeclimate.com/github/ruby-git/ruby-git.png)](https://codeclimate.com/github/ruby-git/ruby-git)
-
-* [Summary](#summary)
-* [v2.x Release](#v2x-release)
-* [Install](#install)
-* [Major Objects](#major-objects)
-* [Errors Raised By This Gem](#errors-raised-by-this-gem)
-* [Specifying And Handling Timeouts](#specifying-and-handling-timeouts)
-* [Examples](#examples)
-* [Ruby version support policy](#ruby-version-support-policy)
-* [License](#license)
+[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-%23FE5196?logo=conventionalcommits&logoColor=white)](https://conventionalcommits.org)
+
+- [📢 We've Switched to Conventional Commits 📢](#-weve-switched-to-conventional-commits-)
+- [Summary](#summary)
+- [Install](#install)
+- [Major Objects](#major-objects)
+- [Errors Raised By This Gem](#errors-raised-by-this-gem)
+- [Specifying And Handling Timeouts](#specifying-and-handling-timeouts)
+- [Examples](#examples)
+- [Ruby version support policy](#ruby-version-support-policy)
+- [License](#license)
+
+## 📢 We've Switched to Conventional Commits 📢
+
+To enhance our development workflow, enable automated changelog generation, and pave
+the way for Continuous Delivery, the `ruby-git` project has adopted the [Conventional
+Commits standard](https://www.conventionalcommits.org/en/v1.0.0/) for all commit
+messages.
+
+Going forward, all commits to this repository **MUST** adhere to the Conventional
+Commits standard. Commits not adhering to this standard will cause the CI build to
+fail. PRs will not be merged if they include non-conventional commits.
+
+A git pre-commit hook may be installed to validate your conventional commit messages
+before pushing them to GitHub by running `bin/setup` in the project root.
+
+Read more about this change in the [Commit Message Guidelines section of
+CONTRIBUTING.md](CONTRIBUTING.md#commit-message-guidelines)
 
 ## Summary
 
@@ -34,31 +51,6 @@ Get started by obtaining a repository object by:
 
 Methods that can be called on a repository object are documented in [Git::Base](https://rubydoc.info/gems/git/Git/Base)
 
-## v2.x Release
-
-git 2.0.0 has recently been released. Please give it a try.
-
-**If you have problems with the 2.x release, open an issue and use the 1.x version
-instead.** We will do our best to fix your issues in a timely fashion.
-
-**JRuby on Windows is not yet supported by the 2.x release line. Users running JRuby
-on Windows should continue to use the 1.x release line.**
-
-The changes in this major release include:
-
-* Added a dependency on the activesupport gem to use the deprecation functionality
-* Create a policy of supported Ruby versions to support only non-EOL Ruby versions
-* Create a policy of supported Git CLI versions (released 2020-12-25)
-* Update the required Ruby version to at least 3.0 (released 2020-07-27)
-* Update the required Git command line version to at least 2.28
-* Update how CLI commands are called to use the [process_executer](https://github.com/main-branch/process_executer)
-  gem which is built on top of [Kernel.spawn](https://ruby-doc.org/3.3.0/Kernel.html#method-i-spawn).
-  See [PR #684](https://github.com/ruby-git/ruby-git/pull/684) for more details
-  on the motivation for this implementation.
-
-The `master` branch will be used for `2.x` development. If needed, fixes for `1.x`
-version will be done on the `v1` branch.
-
 ## Install
 
 Install the gem and add to the application's Gemfile by executing:

data/Rakefile

@@ -58,3 +58,10 @@ task :'test:gem' => :install do
 
   puts 'Gem Test Succeeded'
 end
+
+# Make it so that calling `rake release` just calls `rake release:rubygem_push` to
+# avoid creating and pushing a new tag.
+
+Rake::Task['release'].clear
+desc 'Customized release task to avoid creating a new tag'
+task release: 'release:rubygem_push'

data/lib/git/lib.rb

@@ -294,6 +294,7 @@ module Git
     #   * 'tree' [String] the tree sha
     #   * 'author' [String] the author of the commit and timestamp of when the changes were created
     #   * 'committer' [String] the committer of the commit and timestamp of when the commit was applied
+    #   * 'merges' [Boolean] if truthy, only include merge commits (aka commits with 2 or more parents)
     #
     # @raise [ArgumentError] if the revision range (specified with :between or :object) is a string starting with a hyphen
     #
@@ -305,6 +306,7 @@ module Git
 
       arr_opts << '--pretty=raw'
       arr_opts << "--skip=#{opts[:skip]}" if opts[:skip]
+      arr_opts << '--merges' if opts[:merges]
 
       arr_opts += log_path_options(opts)
 

data/lib/git/log.rb

@@ -133,11 +133,16 @@ module Git
       return self
     end
 
+    def merges
+      dirty_log
+      @merges = true
+      return self
+    end
+
     def to_s
       self.map { |c| c.to_s }.join("\n")
     end
 
-
     # forces git log to run
 
     def size
@@ -184,7 +189,7 @@ module Git
         log = @base.lib.full_log_commits(
           count: @max_count, all: @all, object: @object, path_limiter: @path, since: @since,
           author: @author, grep: @grep, skip: @skip, until: @until, between: @between,
-          cherry: @cherry
+          cherry: @cherry, merges: @merges
         )
         @commits = log.map { |c| Git::Object::Commit.new(@base, c['sha'], c) }
       end

data/lib/git/version.rb

@@ -3,5 +3,5 @@
 module Git
   # The current gem version
   # @return [String] the current gem version.
-  VERSION='3.0.1'
+  VERSION='3.1.0'
 end

data/package.json

@@ -0,0 +1,10 @@
+{
+  "devDependencies": {
+    "@commitlint/cli": "^19.8.0",
+    "@commitlint/config-conventional": "^19.8.0",
+    "husky": "^9.1.7"
+  },
+  "scripts": {
+    "prepare": "husky"
+  }
+}

data/release-please-config.json

@@ -0,0 +1,36 @@
+{
+  "bootstrap-sha": "31374263eafea4e23352494ef4f6bea3ce62c1b5",
+  "packages": {
+    ".": {
+      "release-type": "ruby",
+      "package-name": "git",
+      "changelog-path": "CHANGELOG.md",
+      "version-file": "lib/git/version.rb",
+      "bump-minor-pre-major": true,
+      "bump-patch-for-minor-pre-major": true,
+      "draft": false,
+      "prerelease": false,
+      "include-component-in-tag": false,
+      "pull-request-title-pattern": "chore: release v${version}",
+      "changelog-sections": [
+        { "type": "feat",     "section": "Features",      "hidden": false },
+        { "type": "fix",      "section": "Bug Fixes",     "hidden": false },
+        { "type": "build",    "section": "Other Changes", "hidden": false },
+        { "type": "chore",    "section": "Other Changes", "hidden": false },
+        { "type": "ci",       "section": "Other Changes", "hidden": false },
+        { "type": "docs",     "section": "Other Changes", "hidden": false },
+        { "type": "perf",     "section": "Other Changes", "hidden": false },
+        { "type": "refactor", "section": "Other Changes", "hidden": false },
+        { "type": "revert",   "section": "Other Changes", "hidden": false },
+        { "type": "style",    "section": "Other Changes", "hidden": false },
+        { "type": "test",     "section": "Other Changes", "hidden": false }
+      ]
+    }
+  },
+  "plugins": [
+    {
+      "type": "sentence-case"
+    }
+  ],
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
+}

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: git
 version: !ruby/object:Gem::Version
-  version: 3.0.1
+  version: 3.1.0
 platform: ruby
 authors:
 - Scott Chacon and others
@@ -194,11 +194,16 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".commitlintrc.yml"
 - ".github/issue_template.md"
 - ".github/pull_request_template.md"
 - ".github/workflows/continuous_integration.yml"
+- ".github/workflows/enforce_conventional_commits.yml"
 - ".github/workflows/experimental_continuous_integration.yml"
+- ".github/workflows/release.yml"
 - ".gitignore"
+- ".husky/commit-msg"
+- ".release-please-manifest.json"
 - ".yardopts"
 - CHANGELOG.md
 - CONTRIBUTING.md
@@ -206,7 +211,6 @@ files:
 - LICENSE
 - MAINTAINERS.md
 - README.md
-- RELEASING.md
 - Rakefile
 - git.gemspec
 - lib/git.rb
@@ -236,14 +240,16 @@ files:
 - lib/git/working_directory.rb
 - lib/git/worktree.rb
 - lib/git/worktrees.rb
+- package.json
+- release-please-config.json
 homepage: http://github.com/ruby-git/ruby-git
 licenses:
 - MIT
 metadata:
   homepage_uri: http://github.com/ruby-git/ruby-git
   source_code_uri: http://github.com/ruby-git/ruby-git
-  changelog_uri: https://rubydoc.info/gems/git/3.0.1/file/CHANGELOG.md
-  documentation_uri: https://rubydoc.info/gems/git/3.0.1
+  changelog_uri: https://rubydoc.info/gems/git/3.1.0/file/CHANGELOG.md
+  documentation_uri: https://rubydoc.info/gems/git/3.1.0
 rdoc_options: []
 require_paths:
 - lib

data/RELEASING.md

@@ -1,85 +0,0 @@
-<!--
-# @markup markdown
-# @title Releasing
--->
-
-# How to release a new git.gem
-
-Releasing a new version of the `git` gem requires these steps:
-
-* [Install Prerequisites](#install-prerequisites)
-* [Determine the SemVer release type](#determine-the-semver-release-type)
-* [Create the release](#create-the-release)
-* [Review the CHANGELOG and release PR](#review-the-changelog-and-release-pr)
-* [Manually merge the release PR](#manually-merge-the-release-pr)
-* [Publish the git gem to RubyGems.org](#publish-the-git-gem-to-rubygemsorg)
-
-## Install Prerequisites
-
-The following tools need to be installed in order to create the release:
-
-* [create_githhub_release](https://github.com/main-branch/create_github_release) is used to create the release
-* [git](https://git-scm.com) is used by `create-github-release` to interact with the local and remote repositories
-* [gh](https://cli.github.com) is used by `create-github-release` to create the release and PR in GitHub
-
-On a Mac, these tools can be installed using [gem](https://guides.rubygems.org/rubygems-basics/) and [brew](https://brew.sh):
-
-```shell
-$ gem install create_github_release
-...
-$ brew install git
-...
-$ brew install gh
-...
-$
-```
-
-## Determine the SemVer release type
-
-Determine the SemVer version increment that should be applied for the new release:
-
-* `major`: when the release includes incompatible API or functional changes.
-* `minor`: when the release adds functionality in a backward-compatible manner
-* `patch`: when the release includes small user-facing changes that are
-  backward-compatible and do not introduce new functionality.
-
-## Create the release
-
-Create the release using the `create-github-release` command. If the release type
-is `major`, the command is:
-
-```shell
-create-github-release major
-```
-
-Follow the directions given by the `create-github-release` command to finish the
-release. Where the instructions given by the command differ than the instructions
-below, follow the instructions given by the command.
-
-## Review the CHANGELOG and release PR
-
-The `create-github-release` command will output a link to the CHANGELOG and the PR
-it created for the release. Review the CHANGELOG and have someone review and approve
-the release PR.
-
-## Manually merge the release PR
-
-It is important to manually merge the PR so a separate merge commit can be avoided.
-Use the commands output by the `create-github-release` which will looks like this
-if you are creating a 2.0.0 release:
-
-```shell
-git checkout master
-git merge --ff-only release-v2.0.0
-git push
-```
-
-This will automatically close the release PR.
-
-## Publish the git gem to RubyGems.org
-
-Finally, publish the git gem to RubyGems.org using the following command:
-
-```shell
-rake release:rubygem_push
-```