Add agent guidance and opt-in GitHub release migration - #28
Merged
Merged
Conversation
samuel-williams-shopify
deleted the
modernize-agent-release-migration
branch
September 22, 2026 09:54
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.
Make modernization aware of gems using
bake-gem-github, and provide agent guidance for updating a gem and reviewing the generated changes.Separate commits cover:
[bot]in copyright and gem author lists, preserving human attribution through bot renames.modernize:releases:githubtask to migrate dependencies and release hooks. Regular modernization omits the redundant publishing hook and keeps the correct readme release command whenbake-gem-githubis declared. Existingbake.rbfiles continue to use the Ollama merge, with instructions to remove the obsolete publishing call and preserve custom behavior.bake-gem-github ~> 0.5.0and regenerate release validation and review rules. Release PRs must contain one commit; ordinary PRs can contain multiple commits and use rebase merging when enabled in repository settings.The migration is outside the default task and does not change remote settings.
Validation: 72 tests / 169 assertions pass; Covered reports 502/502 lines exercised. RuboCop and documentation coverage (40/40 definitions) pass. The gem builds with the context and template included, and
agent:context:installdiscovers the new guide. Regenerated release files are stable on a second setup update.