Proof of concept for updating each gem in its own git commit #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closed in favor of #53 |
mattbrictson
added a commit
that referenced
this pull request
Sep 19, 2024
…pecified (#53) Sometimes, updating gems can lead to bugs or regressions. To facilitate troubleshooting, this PR introduces the ability to commit each selected gem update in its own git commit, complete with a descriptive commit message. You can then make use of tools like `git bisect` to more easily find the update that introduced the problem. To enable this behavior, pass the `--commit` option: ``` bundle update-interactive --commit ``` The gems you select to be updated will be applied in separate commits, like this: ``` * c9801382 Update activeadmin 3.2.2 → 3.2.3 * 9957254b Update rexml 3.3.5 → 3.3.6 * 4a4f2072 Update sass 1.77.6 → 1.77.8 ``` Supersedes #50 and #51. Closes #49.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See discussion in #49