-
Notifications
You must be signed in to change notification settings - Fork 536
Comparing changes
Open a pull request
base repository: ruby-git/ruby-git
base: 5f29124
head repository: ruby-git/ruby-git
compare: feab258
- 8 commits
- 18 files changed
- 1 contributor
Commits on Jul 8, 2025
-
fix: un-deprecate Git::Diff methods
These methods were deprecated with the same thinking that the Git::Log methods were deprecated. However, where Git::Log is a query builder, Git::Diff is (mostly) not... it is a facade over diff, diff_stats, and diff_path_stats. A problem remains with the Git::Diff class in that if you call the #path method after retrieving results, the results are not updated which may cause unexpected results. I'll consider what changes should be made to the Git::Diff class at a later date.
Configuration menu - View commit details
-
Copy full SHA for 761b6ff - Browse repository at this point
Copy the full SHA 761b6ffView commit details -
fix: report correct line number in deprecation warnings
ActiveSupport::Deprecation is designed to report the line where the deprecated method is called (one level up the call stack), not where the warning itself is defined. The previous implementation triggered warnings from an internal helper method, causing them to report the location with the Git gem. This commit moves the `warn` call into the public-facing deprecated method, ensuring the warning correctly points to the user's code that should be changed.
Configuration menu - View commit details
-
Copy full SHA for cca0deb - Browse repository at this point
Copy the full SHA cca0debView commit details -
fix: correct the deprecation horizon for Git deprecations
Correctly report that the current deprecations will be removed by version 5.0.0 of the git gem.
Configuration menu - View commit details
-
Copy full SHA for b7b7f38 - Browse repository at this point
Copy the full SHA b7b7f38View commit details -
fix: internally create a Stash with non-deprecated initializer args
this is so that non-deprecated use of this gem will not produce deprecation warnings that the user can't fix.
Configuration menu - View commit details
-
Copy full SHA for 8b9b9e2 - Browse repository at this point
Copy the full SHA 8b9b9e2View commit details -
test: update all tests to not use deprecated features
Several methods, arguments, and behaviors were deprecated but the tests were not updated to use alternates. This caused a lot of deprecation warnings when running the tests.
Configuration menu - View commit details
-
Copy full SHA for 33ab0e2 - Browse repository at this point
Copy the full SHA 33ab0e2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1de27da - Browse repository at this point
Copy the full SHA 1de27daView commit details -
test: make tests that emit a deprecation warning fail
Deprecation warnings should not be ignored. This is important so that: * when a user sees a deprecation warning, they can be confident it is coming from their code and not this gem * test output is clean and does not contain noisey deprecation warnings Tests whose purpose is to test that a deprecation warning is issued in the right circumstance should mock Git::Deprecation#warn to avoid raising an error.
Configuration menu - View commit details
-
Copy full SHA for 7e211d7 - Browse repository at this point
Copy the full SHA 7e211d7View commit details -
Configuration menu - View commit details
-
Copy full SHA for feab258 - Browse repository at this point
Copy the full SHA feab258View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 5f29124...feab258