Heh, that’s how I found my way here @fool
Thanks for explaining @fool – that’s really interesting, and unexpected! I’ve confirmed now that when I allow the builds to having via github webhooks (eg, branch deploys or master updates) then the prefixed GATSBY_ magic substitution happen as expected.
Is there a way I can leverage the Netlify CI builds when using netlify deploy
to test deploys of WIP code? I guess I expected this would work because I have a build
command defined in my netlify.toml which leads to a gatsby build
, but now I think this may be irrelevant.
edit: Hmm as an update, I’ve discovered that process.env.DEPLOY_URL
is undefined
in a PR preview deploy, from the context of a function. Hmm this I’m less sure how to work around.