Skip to content

Rename gem to git-author-report#17

Merged
wteuber merged 1 commit into
masterfrom
chore/rename-gem-git-author-report
Jun 23, 2026
Merged

Rename gem to git-author-report#17
wteuber merged 1 commit into
masterfrom
chore/rename-gem-git-author-report

Conversation

@wteuber

@wteuber wteuber commented Jun 23, 2026

Copy link
Copy Markdown
Owner

RubyGems rejected publishing git-report — its similarity check normalizes names by stripping separators, so git-reportgitreport, which collides with the existing gitreport gem.

Renames the gem and repository to git-author-report. The executable stays git-report, so the tool is still invoked as git report — no UX change for users.

Changes

  • git-report.gemspecgit-author-report.gemspec; updated name, homepage, source_code_uri.
  • README/CHANGELOG: gem name, gem install/gem uninstall commands, badges, and repo URLs updated. Executable (git-report) and command (git report) references left unchanged.

Verified locally (Ruby 4.0.4)

  • gem build git-author-report.gemspec → builds git-author-report-1.0.0.gem.
  • ruby test/coverage.rb → 14 runs, 0 failures, 100% coverage. RuboCop clean.

Publishing v1.0.0 to RubyGems + git tag + GitHub release follows after merge.

RubyGems rejected `git-report` as too similar to the existing `gitreport`
gem. Rename the gem and repository to `git-author-report`; the executable
stays `git-report`, so the tool is still invoked as `git report`.

- gemspec: rename file to git-author-report.gemspec; update name, homepage,
  and source_code_uri to the renamed repo.
- README/CHANGELOG: update gem name, install/uninstall commands, badges, and
  repository URLs. Executable and `git report` command references unchanged.
@wteuber wteuber merged commit 0c44408 into master Jun 23, 2026
8 checks passed
@wteuber wteuber deleted the chore/rename-gem-git-author-report branch June 23, 2026 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant