Open stringparser opened 3 years ago
automating this might be risky in case it overrides BUILD_VARIANT by mistake.
@salimhb if that is risky we might not want to do an automatically git push
as part of this script?
@salimhb if that is risky we might not want to do an automatically
git push
as part of this script?
Yes, especially that pushing will deploy automatically. Instead of this script, I suggest adding these instructions in the README with a note about the environment variables.
@salimhb, @bitboxer Hm, not sure if I understand but builds are done in vercel
right? Also I think if is this problematic we could use the branch to determine the build (no BUILD_VARIANT
environment variable I mean).
These branches are literally there only to set the BUILD_VARIANT (see the diff) If there's a way to handle this in Vercel, we wouldn't have needed these branches to start with ;)
These branches are literally there only to set the BUILD_VARIANT (see the diff) If there's a way to handle this in Vercel, we wouldn't have needed these branches to start with ;)
Yes yes. I see that but I don't know if we need the environment variable. We can simply use git to get the branch name and do the build based on this.
Adding a deploy script.
Maybe we should include a promotion in Semaphore too or instead of this?