Netlify Deploy Bug [.env on repo change]

Support
1

Hello- I just wanted to raise an alert of what I believe to be a bug that is re-creatable 100% of the time so far.

When updating the repository of an existing deployed site to a new repository, the deploy setup prompts you to add any relevant environment variables for the new deployment.

Regardless of what you put in these environment variables, they will not save with the new deployment [this is what I believe to be the bug], and it will revert to the previously deployed environment variables, but with the new production frontend.

So far, this is happening on every project type for me. Updating to a new repo specifically (which doesn’t happen that often, but still) is not saving the new environment variables and is keeping the previous ones for the next deploy.

3

Hey @cormeistro :wave:,
Thanks for reaching out!

We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.

Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.

We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.

Thanks for being here, and keep an eye out for that email from us!