Merged
Conversation
OutlawAndy
force-pushed
the
major-structure-cleanup-part-1
branch
2 times, most recently
from
bc1bc85 to
ad046c7
Compare
OutlawAndy
force-pushed
the
major-structure-cleanup-part-1
branch
from
ad046c7 to
80d8710
Compare
wesrich
approved these changes
Feb 13, 2026
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
2 participants
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.
Why?
I'm trying to move this repository closer to Gem best-practices. This PR focuses mostly on having a single entry-point to load the whole gem. Though it also introduces a BaseGenerator for all others to inherit from. We're still breaking the cardinal rule of RubyGems (introducing multiple namespaces), but I have a plan to tackle that next..
Pre-merge checklist
bin/bump_versionorbin/bump_version --patch