Hi, We've just started implementing semantic versioning to our CI process and have just run into a small issue that we can't figure out from the docs. What happens: - Build triggers in Seed from GitHub push - Seed install, compile, build as normal - Build spec defines some extra steps during before_compile, including a

semantic-release

- semantic-release pushes back to GitHub with generated

CHANGELOG

file   - commit:

<whatever we need> [skip ci]

-

<!>

this commit triggers another build in Seed as it's a push to GitHub That last step is the problem. A lot of other CI/CD tools support rules for skipping commits such as "contains [skip ci]". Normally, we would work around this by access the last commit from the git repo and checking it in the build spec, but your docs do not show any way to get the current repo name, or commit message inside the buildspec; there is only

$SEED_BRANCH

that relates to the git repo. So two questions: 1. Is there an environment variable for

$SEED_COMMIT

or something equivalent so we can put in a script on

before_compile

to force a skip? 2. Is there a way to force a skip from build spec? Thanks

Hey @Kyle Boucher, I’m getting the team to put in

[skip ci]

support. Should have something very soon. I will keep you posted.