Those assume that when BRANCH_NAME == "master", it is a push to the main repository.
It is quite common for people to accidentally build from the 'master' of forks, and submit PRs from that branch.
While it is highly undesirable that PRs come from master, and we intend to prevent it with a gitmate plugin, .ci/semaphore.docker.sh and .ci/semaphore.answers.sh should not break as a result. They should detect pull requests, and not do the deploy-preparation steps.
Those assume that when BRANCH_NAME == "master", it is a push to the main repository.
It is quite common for people to accidentally build from the 'master' of forks, and submit PRs from that branch.
While it is highly undesirable that PRs come from master, and we intend to prevent it with a gitmate plugin,
.ci/semaphore.docker.sh
and.ci/semaphore.answers.sh
should not break as a result. They should detect pull requests, and not do the deploy-preparation steps.c.f. https://github.com/coala/corobo/pull/582#issuecomment-405707141 which broke because of this, and probably other PRs also.