Should the

SEED_BRANCH

environment variable be the source or target branch for an auto deployed gitlab MR? I had expected it to be the source branch but it seems to be "master" when I echo it in the post-deploy phase - is this a bug or a feature? 🐛/🦋

@Robert Chandler I don't use gitlab, but have you tried echoing out the

SEED_STAGE_BRANCH

environment variable to see if that's the branch you expect it to be? According to the docs: https://seed.run/docs/adding-a-build-spec#build-environment-variables that envvar should contain the branch name that's being auto-deployed from:

• The name of the git branch the stage is auto-deployed from. If the stage is not auto-deployed, the value is not defined.

Because I'm deploying from a PR rather than a feature branch the

SEED_STAGE_BRANCH

is undefined. After re-reading the docs it does seem like it is indeed a features that the

SEED_BRANCH

env var is the target branch not the source branch. In which case it seems like it's not possible to get the source branch name for an auto-deployed PR branch . Other options include triggering the deployment manually from gitlab ci, using the commit id or switching to github

Hey guys, sorry about the delay getting to this. @Robert Chandler we just added two more build environment variables:

SEED_PULL_REQUEST_SOURCE_BRANCH
SEED_PULL_REQUEST_TARGET_BRANCH

They hold the value for the source and target branch names.

Brilliant, thank you!

Hey @Robert Chandler, those two environment variables should've already been deployed.

I just saw they were working in our newest PR branch, I'm now checking older PR branches