Detect RubyGems projects and alternate Bundler manifests - #203
Merged
Merged
Conversation
andrew
force-pushed
the
ruby-package-manager-detection
branch
from
October 1, 2026 13:54
e6e0f45 to
5fa9dce
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Detect RubyGems for gemspec-only projects, nested gems, and Hoe declarations. RubyGems and Bundler can both be reported when a project uses both tools.
Add Bundler detection and dependency parsing for
gems.rbandgems.locked. When both manifest layouts exist, prefergems.rband its lockfile so an ignoredGemfile.lockdoes not contribute dependencies or appear as the active lockfile.Fixes #201