feat(site): clarify why secret name is disabled when editing#26553
Open
blinkagent[bot] wants to merge 2 commits into
Open
feat(site): clarify why secret name is disabled when editing#26553blinkagent[bot] wants to merge 2 commits into
blinkagent[bot] wants to merge 2 commits into
Conversation
Adds helper text under the disabled Name field in the Edit secret
dialog explaining that the name cannot be changed after creation
and that users must delete and recreate the secret to rename it.
The name is used as the resource identifier in the API path
(PATCH /api/v2/users/{user}/secrets/{name}) and is not part of
UpdateUserSecretRequest, so renaming is not supported server-side.
matifali
approved these changes
Jun 20, 2026
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
1 participant
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.
Adds helper text under the disabled
Namefield in the Edit secret dialog so users understand why it can't be changed:Matches the existing pattern used elsewhere (e.g. AI settings). The secret name is the resource identifier in the API path (
PATCH /api/v2/users/{user}/secrets/{name}) andUpdateUserSecretRequesthas nonamefield, so rename isn't supported server-side.Created on behalf of @matifali.