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

XP ref: explanation; cycle detection; comparison to packages #3574

Closed
Tracked by #3362
jtcohen6 opened this issue Jun 20, 2023 · 0 comments · Fixed by #3577
Closed
Tracked by #3362

XP ref: explanation; cycle detection; comparison to packages #3574

jtcohen6 opened this issue Jun 20, 2023 · 0 comments · Fixed by #3577
Assignees
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows

Comments

@jtcohen6
Copy link
Collaborator

jtcohen6 commented Jun 20, 2023

@jtcohen6 jtcohen6 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear idea Proposes an idea for new content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) labels Jun 20, 2023
@jtcohen6 jtcohen6 added this to the dbt Core v1.6 Documentation milestone Jun 20, 2023
@jtcohen6 jtcohen6 self-assigned this Jun 20, 2023
@runleonarun runleonarun added the priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows label Jun 22, 2023
@runleonarun runleonarun removed the idea Proposes an idea for new content label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants