ruby_git 0.2.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 740fbc545a60561d555d5d698dc6303d150a7fa4eed583afbf70facd70610502
-  data.tar.gz: '094fb5b8d53b28c240074f6c874fddaf503f2a5f4218207a437205c0aec4118e'
+  metadata.gz: b12470df80fc020031e73898e6332def5b5d6e7c419acb3036a58585263269b7
+  data.tar.gz: d1138d2381fc7272397357105b8e884a78bed2396289608df6dc746896018b4b
 SHA512:
-  metadata.gz: 8be9d5931ea2c500fc07f0f2b0fcb93e7324e8bb156216c0f6adf147c465a41b97e6b1e3f159fe5cae5ff804613eb82b18f4ca7ea41abf4a0d4a5fb34a098444
-  data.tar.gz: d054d7dca124d1da739dab1d7191d81dd2f7ceef900b81b118ad18f0bad2f852eda4d1970da2c169a3f18857e4d804a1efb48ac9fb7fb5b08ba4e592276741bf
+  metadata.gz: f1cbdfcdea413421d06bf15ad2c205866dff32a1b92ffea0b260dbecf31fe62313fb6b355ae81fff9cb0f07fab26af622c90eeb28c1b1e28c63c27a02223e499
+  data.tar.gz: e51b5c257998f8a2c9cad6927bfd1b32d4f397c793b82edd6017a00b4581b9b6f6f00623f05ec9d2052b42a72c62fabc94268bb4caa6b1d6b408a3b2d5041f46

data/.commitlintrc.yml

@@ -0,0 +1,16 @@
+---
+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
+  #
+  # Run `npx commitlint --print-config` to see the current setting for all rules.
+  #
+  body-leading-blank:    [2, 'always']
+  footer-leading-blank:  [2, 'always']

data/.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# Defines who must review pull requests.
+# See https://help.github.com/articles/about-codeowners/ for details.
+
+* @jcouball @main-branch/ruby_git-codeowners

data/.github/workflows/continuous_integration.yml

@@ -0,0 +1,87 @@
+name: Continuous Integration
+
+on:
+  push:
+    branches: [main]
+
+  pull_request:
+    branches: [main]
+
+  workflow_dispatch:
+
+env:
+  # SimpleCov suggests setting the JRuby --debug flag to ensure that coverage
+  # results from JRuby are complete.
+  JRUBY_OPTS: --debug
+  GIT_AUTHOR_NAME: Git Author
+  GIT_AUTHOR_EMAIL: git_author@example.com
+  GIT_COMMITTER_NAME: Git Committer
+  GIT_COMMITTER_EMAIL: git_committer@example.com
+
+# Supported platforms / Ruby versions:
+#  - Ubuntu: MRI (3.1, 3.2, 3.3, 3.4), TruffleRuby (24), JRuby (9.4)
+#  - Windows: MRI (3.1)
+
+jobs:
+  build:
+    name: Ruby ${{ matrix.ruby }} on ${{ matrix.operating-system }}
+
+    runs-on: ${{ matrix.operating-system }}
+    continue-on-error: true
+
+    env:
+      FAIL_ON_LOW_COVERAGE: ${{ matrix.fail_on_low_coverage }}
+
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby: ["3.1", "3.2", "3.3", "3.4"]
+        operating-system: [ubuntu-latest]
+        fail_on_low_coverage: [true]
+        include:
+          - ruby: "3.1"
+            operating-system: windows-latest
+            fail_on_low_coverage: false
+          - ruby: "jruby-9.4"
+            operating-system: ubuntu-latest
+            fail_on_low_coverage: false
+          - ruby: "truffleruby-24"
+            operating-system: ubuntu-latest
+            fail_on_low_coverage: false
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Initialize Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+
+      - name: Run rake
+        run: bundle exec rake
+
+  coverage:
+    name: Report test coverage to CodeClimate
+
+    needs: [build]
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Initialize Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.1
+          bundler-cache: true
+
+      - name: Report test coverage
+        uses: paambaati/codeclimate-action@v9
+        env:
+          CC_TEST_REPORTER_ID: b86e77bc6980a43dc09314502fe13334e0f663770b840628ca0716e6dcdeeb5d
+        with:
+          coverageCommand: bundle exec rake spec
+          coverageLocations: ${{github.workspace}}/coverage/lcov/*.lcov:lcov

data/.github/workflows/enforce_conventional_commits.yml

@@ -0,0 +1,21 @@
+name: Conventional Commits
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  commit-lint:
+    name: Verify Conventional Commits
+
+    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_ruby_builds.yml

@@ -0,0 +1,65 @@
+name: Experimental Ruby Builds
+
+on:
+  push:
+    branches: [main]
+
+  workflow_dispatch:
+
+env:
+  # SimpleCov suggests setting the JRuby --debug flag to ensure that coverage
+  # results from JRuby are complete.
+  JRUBY_OPTS: --debug
+
+# Experimental platforms / Ruby versions:
+#  - Ubuntu: MRI (head), TruffleRuby (head), JRuby (head)
+#  - Windows: MRI (head), JRuby (head), JRuby (9.4)
+
+jobs:
+  build:
+    name: Ruby ${{ matrix.ruby }} on ${{ matrix.operating-system }}
+
+    runs-on: ${{ matrix.operating-system }}
+    continue-on-error: true
+
+    env:
+      FAIL_ON_LOW_COVERAGE: ${{ matrix.fail_on_low_coverage }}
+      GIT_AUTHOR_NAME: Git Author
+      GIT_AUTHOR_EMAIL: git_author@example.com
+      GIT_COMMITTER_NAME: Git Committer
+      GIT_COMMITTER_EMAIL: git_committer@example.com
+
+    strategy:
+      fail-fast: false
+      matrix:
+        fail_on_low_coverage: [true]
+        include:
+          - ruby: head
+            operating-system: ubuntu-latest
+          - ruby: head
+            operating-system: windows-latest
+          - ruby: truffleruby-head
+            operating-system: ubuntu-latest
+            fail_on_low_coverage: false
+          - ruby: jruby-head
+            operating-system: ubuntu-latest
+            fail_on_low_coverage: false
+          - ruby: "jruby-9.4"
+            operating-system: windows-latest
+            fail_on_low_coverage: false
+          - ruby: jruby-head
+            operating-system: windows-latest
+            fail_on_low_coverage: false
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Initialize Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+
+      - name: Run rake
+        run: bundle exec rake

data/.gitignore

@@ -16,3 +16,6 @@ rubocop-report.json
 /Gemfile.lock
 .idea
 .irb_history
+
+node_modules
+package-lock.json

data/.husky/commit-msg

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

data/.markdownlint.yml

@@ -0,0 +1,25 @@
+default: true
+
+# Unordered list indentation
+MD007: { indent: 2 }
+
+# Line length
+MD013: { line_length: 90, tables: false, code_blocks: false }
+
+# Heading duplication is allowed for non-sibling headings
+MD024: { siblings_only: true }
+
+# Do not allow the specified trailing punctuation in a header
+MD026: { punctuation: '.,;:' }
+
+# Order list items must have a prefix that increases in numerical order
+MD029: { style: 'ordered' }
+
+# Lists do not need to be surrounded by blank lines
+MD032: false
+
+# Allow raw HTML in Markdown
+MD033: false
+
+# Allow emphasis to be used instead of a heading
+MD036: false

data/.rubocop.yml

@@ -1,19 +1,17 @@
-AllCops:
-  NewCops: enable
-  # Output extra information for each offense to make it easier to diagnose:
-  DisplayCopNames: true
-  DisplayStyleGuide: true
-  ExtraDetails: true
-  # RuboCop enforces rules depending on the oldest version of Ruby which
-  # your project supports:
-  TargetRubyVersion: 2.6
+inherit_gem:
+  main_branch_shared_rubocop_config: config/rubocop.yml
 
-# The default max line length is 80 characters
-Layout/LineLength:
-  Max: 120
+Metrics/MethodLength:
+  Exclude:
+    - "spec/spec_helper.rb"
+    - "spec/**/*_spec.rb"
 
-# The DSL for RSpec makes it very hard to limit block length:
-Metrics/BlockLength:
+Metrics/AbcSize:
   Exclude:
+    - "spec/spec_helper.rb"
     - "spec/**/*_spec.rb"
-    - "*.gemspec"
+
+AllCops:
+  # Pin this project to Ruby 3.1 in case the shared config above is upgraded to 3.2
+  # or later.
+  TargetRubyVersion: 3.1

data/.yardopts

@@ -2,4 +2,9 @@
 --hide-void-return
 --markup-provider=redcarpet
 --markup markdown
-- CHANGELOG.md CONTRIBUTING.md MAINTAINERS.md RELEASING.md LICENSE.md
+--readme README.md
+- PLAN.md
+- CHANGELOG.md
+- CONTRIBUTING.md
+- RELEASING.md
+- LICENSE.txt

data/CHANGELOG.md

@@ -1,5 +1,63 @@
 # Change Log
 
+## v0.3.1 (2025-03-28)
+
+[Full Changelog](https://github.com/main-branch/ruby_git/compare/v0.3.0..v0.3.1)
+
+Changes since v0.3.0:
+
+* fbadc20 docs: update the gem description
+
+## v0.3.0 (2025-03-28)
+
+[Full Changelog](https://github.com/main-branch/ruby_git/compare/v0.2.0..v0.3.0)
+
+Changes since v0.2.0:
+
+* 89cf543 chore: add the implementation plan
+* 3e952c0 feat: add status report entry filters
+* 301c7b7 feat: support git add via Worktree#add
+* 72020b9 feat: add support to passing path specs to Worktree#status
+* 324a472 test: add tests to verify that Worktree#status builds the right git command
+* c07b3be feat: make Worktree#clone work if clone_to path is not given
+* d7a3232 feat: add Worktree#status
+* 7bae4b6 feat: implement RubyGit::Worktree#status
+* f75e0ec chore: rename working tree to worktree
+* 918487c chore: run git commands using RubyGit::CommandLine.run
+* 8a5b204 fix: fix tests failing on Windows for platform-specific reasons
+* 19eb327 fix: make it so command-line-test script runs in Windows
+* 7fb57c5 refactor: change the way that the git command is run
+* 6efdf53 chore: update process_executer dependency to 3.0
+* 834b33d test: add command line tool to run to test running the command line
+* e74affb chore: make it easier to identify the platform and ruby engine in scripts
+* ceaf40d build: remove semver pr label check
+* 6e56dd0 build: enforce conventional commit message formatting
+* 209c408 Replace NullLogger with Logger.new(File::NULL)
+* 9b23e0f Use shared Rubocop config
+* acb286e Update copyright notice in this project
+* 549d8fb Update links in gemspec
+* 6de1b82 Use standard badges at the top of the README
+* 1fa584e Update yardopts with new standard options
+* 872cd1b Rename "markdown.yml" to ".markdown.yml"
+* ec8299a Standardize YARD and Markdown Lint configurations
+* 1862fc9 Update CODEOWNERS file
+* 6de3eea Set JRuby --debug option when running tests in GitHub Actions workflows
+* 50fda86 Integrate simplecov-rspec into the project
+* 4b7410b Use create-github-release for creating releases
+* 5fd999b Reset CodeClimate code coverage reporter id
+* 7944490 Update continuous integration and experimental ruby builds
+* 943c687 Enforce the use of semver tags on PRs
+* 4e7126a Update minimum required Ruby to 3.1
+* 359c358 Don't enforce coverage % in an RSpec dry run (#30)
+* efa2c90 Use GitHub Actions for CI Builds (#29)
+* d1ca85b Upgrade to Rubocop 1.0 (#25)
+* 6c8fd7a Rename Worktree class to WorkingTree (#24)
+* 88f7471 Remove MAINTAINERS.md from yard documentation (#23)
+* a55042d Add logging to the RubyGit gem (#22)
+* 9a95a32 Redesign RubyGit::FileHelpers.which (#20)
+* 9bb7dc0 Allow members of @main-branch/ruby_git-codeowners to do code review approvals. (#19)
+* 401e1fd Release v0.2.0 (#18)
+
 ## [v0.2.0](https://github.com/main-branch/ruby_git/releases/tag/v0.2.0) (2020-10-12)
 
 [Full Changelog](https://github.com/main-branch/ruby_git/compare/v0.1.3...v0.2.0)

data/CONTRIBUTING.md

@@ -46,8 +46,8 @@ Follow the instructions in the pull request template.
 
 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.
+Once your pull request is ready for review, request a review from at least one of the
+[code owners](https://github.com/orgs/main-branch/teams/ruby_git-codeowners/members).
 
 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 main again if other
@@ -70,8 +70,8 @@ All pull requests must meet these requirements:
 ### Unit tests
   * All changes must be accompanied by new or modified RSpec unit tests
   * The entire test suite must pass when `bundle exec rake spec` is run from the
-    project's local working copy
-  * The unit test suite must maintain 100% code coverage to pass 
+    project's local working tree
+  * The unit test suite must maintain 100% code coverage to pass
 
 ### Documentation
   * New and updated public methods must have [YARD](https://yardoc.org/)
@@ -86,7 +86,7 @@ All pull requests must meet these requirements:
 ### Continuous Integration
   * All tests must pass in the project's [Travis CI](https://travis-ci.org/main-branch/ruby_git)
     build before the pull request will be merged.
-  * You can simulate what happens in the Travis CI build by running `bundle exec rake` in 
+  * You can simulate what happens in the Travis CI build by running `bundle exec rake` in
     the projects root directory.
 
 ### Other Design Guidelines

data/{LICENSE.md → LICENSE.txt}

@@ -1,6 +1,6 @@
 # MIT License
 
-Copyright (c) 2020 James Couball and contributors
+Copyright (c) 2024 James Couball
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/PLAN.md

@@ -0,0 +1,67 @@
+# RubyGit Implementation Plan
+
+This is the plan for the RubyGit project, which provides an object-oriented wrapper
+around the Git command line. The project follows a clear architecture with three main
+objects: Worktree, Index, and Repository.
+
+Implementation of git commands will follow a logical progression to build upon
+previous functionality and deliver value early. Here is the order:
+
+## Git commands
+
+**1. Basic Repository Operations (Some Already Implemented)**
+
+* ✅ git init
+* ✅ git clone
+* ✅ git status
+* ✅ git add
+* git commit
+* git log
+
+**2. Branch Management**
+
+* git branch (create, list, delete)
+* git checkout/switch
+* git merge
+* git rebase
+
+**3. Remote Operations**
+
+* git remote (add, remove, list)
+* git fetch
+* git pull
+* git push
+
+**4. Advanced Repository Operations**
+
+* git tag
+* git stash
+* git cherry-pick
+* git reset
+* git revert
+
+**5. Specialized Operations**
+
+* git blame
+* git bisect
+* git submodule
+* git worktree
+* git reflog
+
+## Rationale
+
+1. **Start with the basic workflow**: This follows the typical Git workflow that
+   developers use daily. You've already implemented init, clone and status, so add
+   and commit are the natural next steps to complete the basic functionality.
+2. **Branch management**: Once basic repository operations are in place, branch
+   management is essential for any Git workflow.
+3. **Remote operations**: These commands build on local operations but add networking
+   capabilities.
+4. **Advanced operations**: These provide more specialized functionality that builds
+   on the core commands.
+5. **Specialized operations**: These are less commonly used but provide powerful
+   capabilities for specific use cases.
+
+This approach allows functional value to be delivered early while building a
+foundation for more complex operations. It also aligns with my idea of how users
+typically learn and use Git, making the library more intuitive.

data/README.md

@@ -1,17 +1,44 @@
 # RubyGit
 
-**THIS PROJECT IS A WORK IN PROGRESS AND IS NOT USEFUL IN ITS CURRENT STATE**
+This project is not complete, but [{file:PLAN.md implementation plan}](PLAN.md) details what is available
+and the order of implementing new features.
 
 [![Gem Version](https://badge.fury.io/rb/ruby_git.svg)](https://badge.fury.io/rb/ruby_git)
-[![Build Status](https://travis-ci.org/main-branch/ruby_git.svg?branch=main)](https://travis-ci.org/main-branch/ruby_git)
+[![Build Status](https://github.com/main-branch/ruby_git/actions/workflows/continuous_integration.yml/badge.svg)](https://github.com/main-branch/ruby_git/actions/workflows/continuous_integration.yml)
+[![Documentation](https://img.shields.io/badge/Documentation-Latest-green)](https://rubydoc.info/gems/ruby_git/)
+[![Change Log](https://img.shields.io/badge/CHANGELOG-Latest-green)](https://rubydoc.info/gems/ruby_git/file/CHANGELOG.md)
 [![Maintainability](https://api.codeclimate.com/v1/badges/5403e4613b7518f70da7/maintainability)](https://codeclimate.com/github/main-branch/ruby_git/maintainability)
 [![Test Coverage](https://api.codeclimate.com/v1/badges/5403e4613b7518f70da7/test_coverage)](https://codeclimate.com/github/main-branch/ruby_git/test_coverage)
 [![Slack](https://img.shields.io/badge/slack-main--branch/ruby__git-yellow.svg?logo=slack)](https://main-branch.slack.com/archives/C01CHR7TMM2)
 
-RubyGit is an object-oriented wrapper for the `git` command line tool for working with Worktrees
-and Repositories. It tries to make more sense out of the Git command line. See the object model
-in [this Lucid chart diagram](https://app.lucidchart.com/invitations/accept/7df13bab-3383-4683-8cb4-e76d539de93d)
-(requires sign in).
+Git Is Hard™ but it doesn't have to be that way. Git has this reputation because it has an
+underlying model that is more complex than other popular revision control systems
+such as CVS or Subversion. To make matters worse, the `git` command line is vast,
+inconsistently implemented, and does not have a clear mapping between the command-line
+actions and Git's underlying model.
+
+Because of this complexity, beginners tend to memorize a few `git` commands in
+order to get by with a simple workflow without really understanding how Git works
+and the rich set of features it offers.
+
+The RubyGit module provides a Ruby API that is an object-oriented wrapper around
+the `git` command line. It is intended to make automating both simple and complex Git
+interactions easier. To accomplish this, it ties each action you can do with `git` to
+the type of object that action operates on.
+
+There are three main objects in RubyGit:
+ * [Worktree](lib/ruby_git/worktree.rb): The directory tree of actual checked
+   out files. The working tree normally contains the contents of the HEAD commit’s
+   tree, plus any local changes that you have made but not yet committed.
+ * [Index](lib/ruby_git/index.rb): The index is used as a staging area between your
+   working tree and your repository. You can use the index to build up a set of changes
+   that you want to commit together. When you create a commit, what is committed is what is
+   currently in the index, not what is in your working directory.
+ * [Repository](lib/ruby_git/repository.rb): The repository stores the files in a project,
+   their history, and other meta data like commit information, tags, and branches.
+
+The [RubyGit Class Diagram](RubyGit%20Class%20Diagram.svg) shows the main abstractions in
+RubyGit, how they are related, and what actions each can perform.
 
 ## Installation
 
@@ -80,3 +107,28 @@ automatically requires ruby_git.
 ## Contributing
 
 Bug reports and pull requests are welcome on GitHub at https://github.com/main-branch/ruby_git.
+
+### Commit message guidelines
+
+All commit messages must follow the [Conventional Commits
+standard](https://www.conventionalcommits.org/en/v1.0.0/). This helps us maintain a
+clear and structured commit history, automate versioning, and generate changelogs
+effectively.
+
+To ensure compliance, this project includes:
+
+* A git commit-msg hook that validates your commit messages before they are accepted.
+
+  To activate the hook, you must have node installed and run `npm install`.
+
+* A GitHub Actions workflow that will enforce the Conventional Commit standard as
+  part of the continuous integration pipeline.
+
+  Any commit message that does not conform to the Conventional Commits standard will
+  cause the workflow to fail and not allow the PR to be merged.
+
+### Pull request guidelines
+
+All pull requests must be merged using rebase merges. This ensures that commit
+messages from the feature branch are preserved in the release branch, keeping the
+history clean and meaningful.

data/RELEASING.md

@@ -1,58 +1,9 @@
 # How to release a new ruby_git gem
 
-Releasing a new version of the `ruby_git` gem requires these steps:
-  * [Prepare the release](#prepare-the-release)
-  * [Create a GitHub release](#create-a-github-release)
-  * [Build and release the gem](#build-and-release-the-gem)
+Run `create-github-release <release-type>` in the root of a clean working tree.
 
-These instructions use an example where the current release version is `1.0.0`
-and the new release version to be created is `1.1.0.pre1`.
+Where `release-type` is `major`, `minor`, or `patch` depending on the nature of the
+changes. Refer to the labels on each PR since the last release to determine which
+semver release type to specify.
 
-## Prepare the release
-
-On a branch (or fork) of ruby_git, create a PR containing changes to (1) bump the
-version number and (2) update the CHANGELOG.md, and (3) tag the release.
-
-  * Bump the version number
-    * Version number is in lib/ruby_git/version.rb
-    * Follow [Semantic Versioning](https://semver.org) guidelines
-    * `bundle exec bump --no-commit patch` # backwards compatible bug fixes
-    * `bundle exec bump --no-commit minor` # backwards compatible new functionality
-    * `bundle exec bump --no-commit major` # incompatible API changes
-    
-  * Update CHANGELOG.md
-    * `bundle exec rake changelog`
-
-  * Stage the changes to be committed
-    * `git add lib/ruby_git/version.rb CHANGELOG.md`
-
-  * Commit, tag, and push changes to the repository
-    * ```git release v`ruby -I lib -r ruby_git -e 'puts RubyGit::VERSION'` ```
-
-  * Create a PR with these changes, have it reviewed and approved, and merged to main.
-
-## Create a GitHub release
-
-On [the ruby_git releases page](https://github.com/main-branch/ruby_git/releases),
-select `Draft a new release`
-
-  * Select the tag corresponding to the version being released `v1.1.0.pre1`
-  * The Target should be `main`
-  * For the release description, copy the relevant section from the CHANGELOG.md
-    * The release description can be edited later.
-  * Select the appropriate value for `This is a pre-release`
-    * Since `v1.1.0.pre1` is a pre-release, check `This is a pre-release`
-
-## Build and release the gem
-
-Clone [main-branch/ruby_git](https://github.com/main-branch/ruby_git) directly (not a
-fork) and ensure your local working copy is on the main branch
-
-  * Verify that you are not on a fork with the command `git remote -v`
-  * Verify that the version number is correct by running `rake -T` and inspecting
-    the output for the `release[remote]` task
-
-Build the git gem and push it to rubygems.org with the command `rake release`
-
-  * Ensure that your `gem sources list` includes `https://rubygems.org` (in my
-    case, I usually have my work’s internal gem repository listed)
+Follow the directions that `create-github-release` after it prepares the release PR.