This repository was archived by the owner on Sep 30, 2024. It is now read-only.
Chore: remove search console#63322
Merged
Merged
Conversation
fkling
approved these changes
Jun 19, 2024
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The search console page is broken, is not used or maintained, and is only referenced by a series of blog posts years ago. We have product support to remove it.
The links in the blog post that referenced this are already broken due to the removal of
repogroupand changes to the default patterntype, so removing this does not change the state of that blog post. I tried to update the links in that blog post, but it's nontrivial since the referenced code has changed since it was written. I think it's okay for a 4-year-old blog post to have some broken links though, so I don't plan to spend time fixing them.Fixes SRCH-585
Test plan
I ran the stack and checked that
/search/consolenow attempts to resolve as a repo. I did not bother with redirects because of how little this is used, so the risk is very low.