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
CI fails because it cannot find the value for how many splits to make. It's set as a variable here.
Example failed run: https://github.com/dbt-labs/dbt-core/actions/runs/5711486491/job/15473190823?pr=8222
CI runs.
Open a PR from a fork.
No response
n/a
We can either hardcode the value or we can change the trigger to on_pull_request_target
on_pull_request_target
open discussion
The text was updated successfully, but these errors were encountered:
emmyoop
Successfully merging a pull request may close this issue.
Is this a new bug in dbt-core?
Current Behavior
CI fails because it cannot find the value for how many splits to make. It's set as a variable here.
Example failed run: https://github.com/dbt-labs/dbt-core/actions/runs/5711486491/job/15473190823?pr=8222
Expected Behavior
CI runs.
Steps To Reproduce
Open a PR from a fork.
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
We can either hardcode the value or we can change the trigger to
on_pull_request_target
open discussion
The text was updated successfully, but these errors were encountered: