Reposting this as a new thread from New Build Stages
We’re hitting a problem on the AMP project, where Travis jobs in multiple stages appear to be using the same merge commit (and same commit log) even though
origin/master has moved forward.
For details, see the comment at https://github.com/ampproject/amphtml/issues/21527#issuecomment-496717388
Would it be possible to expose the commit SHA of
origin/master at the start of the first stage of a Travis build via an environment variable, so that it can be used by subsequent stages to establish which files have changed by a pull request? This will allow us to not have to rely on the real
origin/master , which is a moving target.