Missing environment variable in GitHub workflow when creating a new project on Nuxthub

[maximepvrt]

Describe the bug
When creating a new project on Nuxthub, I added environment variables through the project configuration. However, after the project was set up on GitHub, I noticed that NUXT_OAUTH_GOOGLE_CLIENT_ID was missing, while NUXT_OAUTH_GOOGLE_CLIENT_SECRET was correctly added.

Expected behavior
All environment variables added in the Nuxthub configuration should be properly copied into the GitHub workflow.

[RihanArfan]

When linking a NuxtHub project to a GitHub repository, NuxtHub automatically copies all environment variables over from Cloudflare. Since secrets cannot be retrieved after being set, they cannot be automatically migrated.

I suspect you've added NUXT_OAUTH_GOOGLE_CLIENT_ID as a secret on Cloudflare. Could you double check from the Cloudflare dashboard under the Pages project settings -> variables (you can choose the environment from the top)?

[maximepvrt]

I double-checked, and NUXT_OAUTH_GOOGLE_CLIENT_ID is indeed a non-encrypted variable in my case. I also tried modifying, but it was only updated for production, while it still hasn't been added to the preview environment. This behavior is quite strange.

Additionally, I don’t understand why NuxtHub doesn’t send secrets to both GitHub and Cloudflare when defining them in NuxtHub. If it's truly impossible to automatically send secrets to GitHub, it would be helpful to have a warning when using GitHub Actions. This way, users would be reminded to update secrets manually if they modify one in NuxtHub.

[RihanArfan]

After linking the project to a GitHub repository, NuxtHub should sync any created environment variables or secrets to the respective GitHub environment. I'm looking into this.

[remihuigen]

Semi related: When removing a secret from NuxtHub Admin, it's not removed in GitHub secrets..