added dbt_groups to docs

[arbiv]

null

Summary by CodeRabbit

• Documentation
  • Added new sections describing the dbt_groups model and table, including details about group properties and metadata, to the dbt artifact and package model documentation.

[linear]

ELE-4409 Collect DBT Group

[github-actions]

👋 @arbiv
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in this pull request.

[coderabbitai]

Walkthrough

The documentation was updated to include new sections describing the dbt_groups model and table. These sections explain that dbt_groups contains metadata about groups configured in the project and its packages, including details such as group name and owner. No changes were made to existing content or public entities.

Changes

File(s)	Change Summary
docs/dbt/dbt-artifacts.mdx	Added a section describing the dbt_groups model, its contents, and data refresh behavior.
docs/dbt/package-models.mdx	Added a section describing the dbt_groups table and its metadata fields.

Poem

In docs we grow, a new tale unfolds,
Of dbt_groups and all it holds.
Group names and owners, now clear as day,
In tables and models, they're here to stay.
With every refresh, the story renews—
Hopping ahead, we document the news!
🐇📚

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/dbt/package-models.mdx (1)

117-123: Use Code Formatting for Column Names

Consider wrapping column names in backticks for consistency and clarity (e.g., group_name, owner).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 788ea52 and 8c2a696.

📒 Files selected for processing (2)

• docs/dbt/dbt-artifacts.mdx (1 hunks)
• docs/dbt/package-models.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: code-quality

🔇 Additional comments (2)

docs/dbt/package-models.mdx (1)

117-123: Ensure the dbt_groups Model Exists in the Codebase

Please verify that the dbt_groups model file is implemented and included in the package (e.g., models/edr/dbt_artifacts/dbt_groups.sql) so the documentation aligns with the actual code.

docs/dbt/dbt-artifacts.mdx (1)

81-84: Validate Artifact Model Implementation

Confirm that the dbt_groups artifact model SQL file exists under the dbt_artifacts folder and is populated on each run, ensuring the docs accurately reflect the package behavior.