Repository navigation
Migrate Danger to danger-pr-comment workflows - #18
Merged
Merged
Conversation
3 tasks
Retain legacy Ruby test compatibility and run Danger on a modern Ruby separately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dblock
force-pushed
the
dblock/danger-migration
branch
from
October 16, 2026 22:54
2c8a645 to
e4b4002
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
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
Replace obsolete mongoid-danger with danger, danger-changelog and danger-pr-comment, using separate run/comment workflows. Keep modern Danger dependencies out of legacy Ruby test jobs and run Danger with Ruby 3.3.
Supersedes #15 on a dedicated branch rebased onto current master; this avoids rewriting the original fork master branch.
AI-assisted implementation and posting on behalf of @dblock.