We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example: https://circleci.com/gh/StackStorm/st2chatops/253
This happens because of several reasons:
HUBOT_SLACK_TOKEN
PACKAGECLOUD_TOKEN
For security reasons these env variables are hidden https://circleci.com/docs/fork-pr-builds/#security-implications-of-running-builds-for-pull-requests-from-forks for forked builds. But it's possible to make some steps optional which require envs. For example HUBOT_SLACK_TOKEN is not needed for the PR builds.
For the moment it means it's hardly possible to accept 3rd party contributions.
The text was updated successfully, but these errors were encountered:
Set PKG_RELEASE=1 number for forked PRs
dcfae43
Avoid failing the build, because PACKAGECLOUD_TOKEN is not available Partially solves StackStorm#47
ebac283
external-scripts.json
No branches or pull requests
Example: https://circleci.com/gh/StackStorm/st2chatops/253
This happens because of several reasons:
HUBOT_SLACK_TOKEN
is providedPACKAGECLOUD_TOKEN
is providedFor security reasons these env variables are hidden https://circleci.com/docs/fork-pr-builds/#security-implications-of-running-builds-for-pull-requests-from-forks for forked builds.
But it's possible to make some steps optional which require envs. For example
HUBOT_SLACK_TOKEN
is not needed for the PR builds.For the moment it means it's hardly possible to accept 3rd party contributions.
The text was updated successfully, but these errors were encountered: