chore: fix dead link to now removed issue#113
Merged
k0kubun merged 1 commit intoruby:masterfrom Apr 22, 2026
Merged
Conversation
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.
Fixes dead link in NEWS.
I understand you were probably trying to stop people filing issues in the places you don't want them; but it has presumably had the side effect of taking all history offline and breaking links like this (to an issue, not a PR) as well as removing important context for some changes PRs.
There's seemingly no way to find any context for the change now, since the issues have been made "closed source" and the commit message at f0f68ba contains no context. As an additional example, #38 also has no context and links to https://github.com/ruby/erb/issues/32 which is now dead. IMHO this is not good.
For the record, as a community member who spends a lot of time doing code archaeology and digging around projects, I really dislike it when projects do this in GitHub. I don't think this is/was a good idea and is against the spirit of open source - because it closes access to information that was open/public and summarily takes others' public contributions private.