Skip to content
New issue

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

index-resources.yml: Add is-workflow-call input #865

Merged
merged 1 commit into from
May 16, 2024

Conversation

joverlee521
Copy link
Contributor

Working around the issue that GITHUB_EVENT_NAME points to the caller workflow context by using an input to flag the workflow_call event.

Workaround based on GitHub Actions discussion
actions/runner#1884 (comment)

Related issue(s)

Follow up to #841

Checklist

  • Checks pass

Working around the issue that `GITHUB_EVENT_NAME` points to the caller
workflow context by using an input to flag the workflow_call event.

Workaround based on GitHub Actions discussion
<actions/runner#1884 (comment)>
@nextstrain-bot nextstrain-bot temporarily deployed to nextstrain-s-separate-i-gscghj May 16, 2024 18:47 Inactive
@joverlee521 joverlee521 merged commit a1df508 into master May 16, 2024
3 of 4 checks passed
@joverlee521 joverlee521 deleted the separate-indexer-fix-2 branch May 16, 2024 18:47
@joverlee521 joverlee521 mentioned this pull request May 16, 2024
7 tasks
joverlee521 added a commit that referenced this pull request May 16, 2024
When the workflow is not triggered by `workflow_call`, then the
`is-workflow-call` input sets the `IS_WORKFLOW_CALL` environment
variable to an empty string. This commit explicitly sets the
default value for `IS_WORKFLOW_CALL` to `false` so that
`./scripts/get-resource-index-ref-matrix` can run the appropriate steps.

Follow up to #865.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants