Repository navigation
Add workflow configuration to release spec fixtures - #56
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Summary
Add optional RSpec fixture setup:
The generated fixture Rakefile loads
ruby-gem-release/rspec, requires the copied project builder, supplies the existing local Provider, Destination, and Hosting adapters, and callsinstall_tasks. Production configuration,run_task, andrelease!are unchanged. Manualproject.write('Rakefile', ...)remains available for custom cases.Builder strings must be a constant path and method. Source paths are encoded with
String#dump; source and Rakefile paths reuse the existing checkout/Git-metadata checks. Invalid arguments and escaping symlinks are rejected before replacing files.Update the lifecycle-hooks example and testing guide. The complete example still copies its real builder and README, verifies the release and development hooks, and now checks both local publication copies against the exact built archive.
Validation
bundle exec rake: 351 examples, no failures; 148 RuboCop files, no offenses.bundle exec rake build.Created by an AI assistant on behalf of @dblock.