fix: update HCP vault links to use current URL patterns #275
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
Realized this was an issue while updating how we're rendering GFM alerts on the Registry website. Basically, the URLs we're using right now are technically valid, but they were using the old URL pattern from before we created the `coder/registry` repo in the first place. The Registry website has logic to handle redirects for these, but it was making the user's browser history messier than they needed to be. ## Changes made - Updated all links in the HCP Vault alert to include `coder` as the namespace
matifali
approved these changes
Jul 31, 2025
This comment was marked as outdated.
This comment was marked as outdated.
Parkreiner
requested review from
DevelopmentCats
and removed request for
DevelopmentCats
DevelopmentCats
approved these changes
Aug 1, 2025
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.
Realized this was an issue while fixing how we're rendering GFM alerts on the Registry website.
Description
Basically, the URLs we're using right now are technically valid, but they were using the old URL pattern from before we created the
coder/registryrepo. The Registry website has logic to handle redirects for these, but we should avoid triggering it as it adds unnecessary entries to the user's browser history.Changes made
coderas the namespaceType of Change
Testing & Validation
bun test)bun run fmt)