Ability to rename an environment #64081
Replies: 13 comments 17 replies
-
|
Hi @greggbjensen, I see the challenge you're facing. Having the ability to rename an environment, especially when you're standardizing naming conventions, would indeed be a helpful feature. This would also simplify the process of managing secrets and environments without having to recreate everything from scratch. I'd recommend submitting this as a feature request directly through the GitHub feedback form. This ensures the GitHub team can evaluate your suggestion. Thanks for sharing your feedback! |
Beta Was this translation helpful? Give feedback.
-
|
+2 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply! |
Beta Was this translation helpful? Give feedback.
-
|
+1 any updates on this? |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
This is a good idea, I will add it to our paper cuts list to try to get to. We are getting pretty full for this year (we have a bunch of paper cuts :D ) but I will ensure this is in the list and considered <3 |
Beta Was this translation helpful? Give feedback.
-
|
I would <3 y'alls thoughts on how this should interact with the fact that if a workflow references an environment that doesn't exist. Github Actions creates it. I guess my worry here is that files being missed in rename would just 'create' new environments. Or should we just block this behavior 👀 |
Beta Was this translation helpful? Give feedback.
-
I am thinking that if the environment does not exist and is being referenced, it should throw either a warning or an error, because I am not sure what the point of creating a new, empty environment would be. it seems like the behavior as you describe makes the potential issue (incorrectly named environments) harder to find than if it failed in build step. This next part may be out of scope, but I think it would be a really cool idea if GitHub could detect recently changed environment names, and then give a warning on the screen like “You recently changed the environment name for previous_environment to new_envirnment. You are still referencing the old environment name. {list of links to take you to that location in your workflow file} |
Beta Was this translation helpful? Give feedback.
-
|
This is so good idea |
Beta Was this translation helpful? Give feedback.
-
|
I'm wondering about this too because I'm trying to test actions and deployments are getting labelled as the environments I made, which I named without thinking they would be used for that |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the bump, but are there any updates? I have one environment where the name no longer makes sense for its current use. I’d recreate it, but since I don’t have access to the original secrets, being able to rename it would be a huge help. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, also wanted this to be as simple as edit name. But seems AI features have become more important than basic requests :( |
Beta Was this translation helpful? Give feedback.
-
|
Still no updates 💔🥀 |
Beta Was this translation helpful? Give feedback.
-
|
Are there any updates on this? |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
If GitHub uses secret names as unique identifiers, I'm curious how Bitbucket's similar repository variables can be renamed. A developer might have effectively lost the key to a secret, and without the ability to rename it, the only alternative deleting and recreating the secret is not possible. For this reason, a rename feature would have been a valuable convenience. |
Beta Was this translation helpful? Give feedback.
-
|
Yet another update ask here ¯_ (ツ)_/¯ Looking forward for an update. |
Beta Was this translation helpful? Give feedback.
-
|
still no updates again 💔🥀 |
Beta Was this translation helpful? Give feedback.
-
|
Yup. Thought I'd scroll down to find it fixed but... yeah. |
Beta Was this translation helpful? Give feedback.
-
|
Any updates on this ? |
Beta Was this translation helpful? Give feedback.
-
|
of course not only more AI being pushed... |
Beta Was this translation helpful? Give feedback.
-
|
2026! |
Beta Was this translation helpful? Give feedback.
-
|
Please |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
We have many secrets set up in our environments, and unfortunately, the initial ones we created start with an uppercase letter. Now we have standardized on all lowercase letters to make common actions easier. However, we cannot rename an existing environment, clone it, or copy the secrets.
It would be great if we could rename an environment to fix this.
Beta Was this translation helpful? Give feedback.
All reactions