solana/.github/workflows
Illia Bobyr 6fb4716e48
ci: Do not produce build artifacts when run in a fork (#30294)
If someone forks the `solana` repo, they should not have access to Slack
or AWS storage locations that hold build artifacts.  Meaning, actions
that interact with that infrastructure will always fail.  It makes sense
to disable these actions in forks.
2023-02-14 00:31:44 -08:00
..
autolock_bot_PR.txt
autolock_bot_closed_issue.txt
client-targets.yml Merge pull request from GHSA-cq9g-c286-6ch7 2022-11-30 00:58:42 +08:00
crate-check.yml ci: fix commit range in push event (#29755) 2023-01-19 12:28:00 +08:00
docs.yml ci: Do not produce build artifacts when run in a fork (#30294) 2023-02-14 00:31:44 -08:00
error-reporting.yml Merge pull request from GHSA-cq9g-c286-6ch7 2022-11-30 00:58:42 +08:00
increment-cargo-version-on-release.yml
label-actions.yml
manage-stale-issues-and-prs.yml Crank Stalebot's operations limit up to a level that should handle all issues 2022-12-28 19:46:41 -08:00
release-artifacts-auto.yml ci: Do not produce build artifacts when run in a fork (#30294) 2023-02-14 00:31:44 -08:00
release-artifacts-manually.yml
release-artifacts.yml
solana-action.yml.txt Fuck this whole web3.js thing (#30062) 2023-02-01 14:34:23 -08:00