workflows: Don't try to upload when running in someone's fork #2296
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.. which we can tell by whether the environment variable is non-empty.
This fixes a problem where, when I push to my own circuitpython fork, which has actions enabled, I eventually get a failure at the upload step. See e.g., https://github.com/jepler/circuitpython/commit/8e9ac593963537f2504efdfeefe28782de68a53f/checks?check_suite_id=315428254 where all board builds fail at the upload step.
This may only affect users who have deliberately enabled actions within their fork, or maybe actions are still a beta/opt in thing at the user level? For instance, checking another random fork that has recently prepared a pull request, there are no actions that ran in the past: https://github.com/sarfata/circuitpython/actions