git 5.0.0 → 5.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5ea415b04fe50fea515b1473234c75d36895517e656b5cd6364f341da888365c
-  data.tar.gz: 8fe3a13cff41bf5391fcb3f3abf78e2bf8b71890247fce51f987490ae2e1691c
+  metadata.gz: 94d97e48dd1d4b34affe837d38258f7b0f7edf02338d0e0def333ac80e147244
+  data.tar.gz: 5367c11505c46d9745d492a97671346531fddfdc3649b445bae9eb2636f87202
 SHA512:
-  metadata.gz: a9e9a4af8f28d31f92b736010c1cf50dd45a965cabd2e63716a6c0f6ab4e8083cf88c9500bb73346f1d454629955da0f0ed11606f929b45369c20e4bd832d53a
-  data.tar.gz: 61eaa74c731cd013916b3adc7a5488a2a24c0b2618d67b9450e41dcd96bbce27936ce8b0fa224c0e6f6a0b4f5ac4dd6acd17633c621a53d4ed8e6940ccc57a57
+  metadata.gz: 4e404e6b31961cf3c71e391ce4898436f07de8dd2ffc37947281f103513241c531e21aa799ae32296ec6ef47d2b1dad465205fd3b0936ee104b6774870805391
+  data.tar.gz: 778bbd70beb547b4574e8d361acc2873320b42bd4b5f190012309a3b90da72d55468a8c5b4adf87a3ed773ab08945e7ac81b3d282c86bb8bda64821282a3c101

data/.github/copilot-instructions.md

@@ -2,95 +2,41 @@
 
 ## Project Overview
 
-ruby-git is a Ruby gem providing a Ruby interface to Git repositories. It wraps
-system calls to the `git` CLI and exposes an API for creating and manipulating repos,
-working with branches/commits/tags/remotes, inspecting history and objects, and
-performing all standard Git operations.
+A Ruby gem providing an interface to Git repositories by wrapping system calls to the
+`git` CLI.
 
-**Status:** Stable. Minimum Ruby 3.2.0, minimum Git 2.28.0. MRI on macOS/Linux/Windows;
-JRuby and TruffleRuby on Linux (JRuby/TruffleRuby on Windows are not tested).
+Read the "Project Context" skill (`.github/skills/project-context/SKILL.md`) for
+design philosophy, technical details, and compatibility requirements.
 
-For architecture details, coding standards, design philosophy, key technical details,
-and compatibility requirements see the
-[Project Context](skills/project-context/SKILL.md) skill.
+This project enforces Conventional Commits. See `.commitlintrc.yml` for allowed types
+and scopes. Never use `#` in the commit message body. Doing so will cause
+commitlint to incorrectly parse the commit message body as a footer. If you need to
+refer to an issue in the body, use `issue 999` instead of `issue #999`. It is still
+fine to use `#` in footer values such as `Closes: #999` or `Refs: #999`.
 
 ## Terminology & Writing Style
 
-- Use American English always. Avoid British English spellings and idioms.
-- **Version strings** — use the most precise form appropriate to the context:
-  - `vN.x` (e.g. `v5.x`, `v4.x`) — the whole major series; use for compatibility
-    statements and upgrade guide scope ("v4.x code works on v5.x").
-  - `vN.0.0` (e.g. `v5.0.0`, `v6.0.0`) — a specific first release; use when
-    precision matters ("removed in v5.0.0", "the foundation delivered in v5.0.0").
-  - `vN.0` — avoid; ambiguous between "minor version 0" and "shorthand for vN.0.0".
-- **RuboCop** — correct capitalization when referring to the tool by name in prose,
-  documentation, or comments.
-- **`rubocop`** — correct form when referring to the command-line executable or gem
-  name (e.g., `gem 'rubocop'`, `bundle exec rubocop`).
-- **Rubocop** — incorrect; never use this form.
-
-## Skill Loading
-
-When a skill applies to a request, read the entire `SKILL.md` file before taking
-any other action. Read from line 1 through EOF with no gaps. Simple code review
-or explanation does not require a skill.
+- Use American English.
+- **Version strings:** Use `vN.x` for major series compatibility (e.g., `v4.x`) and
+  `vN.0.0` for specific releases (e.g., `v5.0.0`). Never use the ambiguous `vN.0`.
+- **RuboCop:** Use `RuboCop` for prose and `rubocop` for CLI or gem names. Never use
+  `Rubocop`.
 
 ## Project Commands
 
 | Purpose | Command |
 | --- | --- |
-| First-time setup | `bin/setup` |
-| Run all tests and linters (CI-equivalent) | `bundle exec rake default` |
-| Run all tests and linters (force parallel) | `bundle exec rake default:parallel` |
-| Run all RSpec tests | `bundle exec rake spec:parallel` |
-| Run RSpec unit tests | `bundle exec rake spec:unit:parallel` |
-| Run RSpec integration tests | `bundle exec rake spec:integration:parallel` |
+| First-time project or new worktree setup | `bin/setup` |
+| Run all tests and linters (CI-equivalent) | `bundle exec rake` |
+| Run all RSpec tests | `bundle exec rake spec` |
+| Run RSpec unit tests | `bundle exec rake spec:unit` |
+| Run RSpec integration tests | `bundle exec rake spec:integration` |
 | Run a specific RSpec spec | `bundle exec rspec <path>` |
 | Run linters | `bundle exec rake rubocop yard build` |
 
-**Test suite:** `spec/` (RSpec) is the sole test suite — all new tests go here.
-
-## Commit Conventions
-
-This project uses [Conventional Commits](https://www.conventionalcommits.org/).
-Automated releases via [release-please](https://github.com/googleapis/release-please).
-
-**Format:** `type[optional scope][!]: description`
-
-**Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`,
-`revert`, `ci`, `build`
-
-**Breaking changes:** Add `!` before `:` and a `BREAKING CHANGE: <description>`
-footer.
-
-**Version bumps:** breaking change → major; `feat` → minor; others → patch.
-
-**Pre-commit hook:** Run `bin/setup` to install a validator.
-
 ## Branch & PR Strategy
 
 | Target | When |
 | --- | --- |
 | `main` | New features, breaking changes, all active development |
 | `4.x` | Security fixes and backward-compatible bug fixes for the v4.x series |
-
-> **Never commit directly to `main` or `4.x`** — this rule must never be violated.
-> Always check `git branch --show-current` before committing. If on a release branch,
-> run `git switch -c <type>/<short-description>` first.
-
-All changes go through a PR from a topic branch.
-
-**Creating a PR:** Use `gh pr create`. Read `.github/pull_request_template.md` for
-the body structure. Complete the [PR Readiness Review](skills/pr-readiness-review/SKILL.md)
-skill first.
-
-## Key Documents
-
-| Document | Purpose |
-| --- | --- |
-| `CONTRIBUTING.md` | Design philosophy, contribution guidelines |
-| `CHANGELOG.md` | Version history (auto-updated by release-please) |
-| `MAINTAINERS.md` | Maintainer list and responsibilities |
-| `AI_POLICY.md` | AI usage policy for this project |
-| `redesign/` | Architecture redesign plans and implementation guide |
-| `.github/skills/` | All Copilot skills |

data/.gitignore

@@ -21,4 +21,7 @@ rubocop-report.json
 # generated git reference docs
 git-reference/
 
+# git versions built by bin/build-git-versions
+git-versions/
+
 tmp

data/.husky/pre-commit

@@ -7,7 +7,7 @@ protected_branches="main 4.x"
 for protected in $protected_branches; do
   if [ "$branch" = "$protected" ]; then
     echo "ERROR: Direct commits to '$branch' are not allowed."
-    echo "       Create a topic branch first:  git switch -c <branch-name>"
+    echo "       Create a topic branch first:  git switch -c <type>/<short-description>"
     exit 1
   fi
 done

data/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "5.0.0"
+  ".": "5.0.2"
 }