forked from dotnet/runtime
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Old repo issue number mapped to new repo issue number (dotnet#31981)
* Old repo issue number mapped to new repo issue number * add explanation
- Loading branch information
1 parent
850b4a2
commit c649e3b
Showing
4 changed files
with
28,066 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
Many of the issues in this repo were originally created in the dotnet/coreclr, dotnet/corefx, and dotnet/core-setup repos, then migrated here to the dotnet/runtime repo. | ||
|
||
In this process their ID numbers inevitably changed. If you have the old ID number, you can find the new ID number by simply navigating to the old URL: your browser will be redirected to the new URL. | ||
|
||
For example, https://github.com/dotnet/coreclr/issues/25 redirects to https://github.com/dotnet/runtime/issues/3858. | ||
|
||
In some circumstances you may have the new URL and want the old one. For example, if you are looking at a migrated issue and wish to search your email or chat logs for a discussion that referred to the old URL. In that case, you can use these mapping files to look up the old ID and find the old URL. | ||
|
Oops, something went wrong.