How do I set an environment variable (a token) across all codespaces? #49192
Replies: 2 comments 1 reply
-
Hi @Milo123459 ! Thanks for reaching out! Based on your scenario, I think it would be worth trying to access your variable via an encrypted codespace secret: https://docs.github.com/en/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces#adding-a-secret. That guide should show you how to set a codespace secret, and share it with various repos! |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I saw on the docs they suggest adding something to the bash profile file, but due to my dotfiles repository being public, I'm not sure exposing the token onto that repository is a good idea. Does anyone know of a better way?
Beta Was this translation helpful? Give feedback.
All reactions