Hello Benjie Kibblewhite, I’ve been looking for a solution for this, and following your post here when you say “The .env file, however, does get committed and deployed”

But using this approach the .env keys will be exposed on the repo, so it’s a no secure approach. It should be a way that Github could recognize env keys, otherwise I can’t see a solution.