Repository navigation
Point repository references at the danger organization - #18
Merged
Merged
Conversation
The repository moved from numbata to the danger organization. GitHub redirects the old location, but new users copying the README or installer would keep depending on that redirect, and the release tooling matches workflow references by the old owner, so the next release would stop updating them. Update the README, installer, gemspec homepage, release preparation pattern, specs, and release docs to the new owner, including the RubyGems trusted publisher owner. Existing workflows pinned to the old owner keep working through the redirect.
Contributor
Danger ReportErrors
|
dblock
approved these changes
Nov 9, 2026
Coverage Report for CI Build 42715954910Coverage remained the same at 100.0%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
numbata
force-pushed
the
point-to-danger-org
branch
from
November 9, 2026 21:50
312bc5d to
6eb1262
Compare
numbata
marked this pull request as ready for review
November 9, 2026 21:51
The changelog links to pull requests under the old owner and only work through GitHub's redirect, so point them at the danger organization. The RELEASERS cleanup note in the release docs names the old owner and describes a variable that no longer exists, so remove it.
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
The plugin now lives in the
dangerorganization, and people who follow the README or run the installer should be sent there directly instead of relying on GitHub's redirect from the old location. This updates every reference to the new owner and keeps the release tooling working, so the next release still bumps the workflow versions in the docs and installer. Existing workflows pinned to the old owner keep working through the redirect.Because the release tooling matches workflow references by owner, the pattern in
scripts/release_preparation.rbchanges together with the README, installer, and specs. Without that, release preparation would no longer find the references to update.