Skip to content

Conversation

aaronsteers
Copy link
Collaborator

@aaronsteers aaronsteers commented Apr 23, 2025

Summary by CodeRabbit

  • Chores
    • Removed the unused comment-text input parameter from several GitHub Actions workflows.
    • Updated workflow configuration to stop passing the comment text as an argument in the slash command dispatch process.
  • New Features
    • Added comprehensive HubSpot data models and schemas for enhanced data integration.
    • Introduced detailed configuration and metadata files to support HubSpot data ingestion and analysis.
    • Added dbt project setup including profiles, packages, and task configurations for streamlined data modeling.
    • Included documentation outlining the HubSpot data models and their usage.

Copy link

coderabbitai bot commented Apr 23, 2025

Warning

Rate limit exceeded

@aaronsteers has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 59 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 3612086 and a51b3c1.

📒 Files selected for processing (4)
  • .github/workflows/fix-command.yml (1 hunks)
  • .github/workflows/generate-command.yml (1 hunks)
  • .github/workflows/lock-command.yml (1 hunks)
  • .github/workflows/poe-command.yml (1 hunks)

Walkthrough

This update removes the comment-text input parameter from several GitHub Actions workflow files: fix-command.yml, generate-command.yml, and lock-command.yml. Additionally, the slash-command-dispatch.yml workflow is modified to stop passing the comment-text value to the slash-command-dispatch action. No other workflow logic, job steps, or permissions are altered in these files.

Besides workflow changes, a new HubSpot data integration setup is added, including a detailed DBML schema for HubSpot data, a comprehensive dbt source configuration YAML file, and multiple configuration files for the dbt project such as dbt_project.yml, packages.yml, profiles.yml, and task definitions. A configuration lock file for the HubSpot Airbyte integration is also introduced. Documentation and .gitignore files for the dbt project are added to support the new data modeling and ingestion setup.

Changes

Files Change Summary
.github/workflows/fix-command.yml
.github/workflows/generate-command.yml
.github/workflows/lock-command.yml
Removed the optional comment-text input parameter from workflow_dispatch inputs.
.github/workflows/slash-command-dispatch.yml Stopped passing the comment-text value as an argument to the slash-command-dispatch action.
build/hubspot/airbyte-interop.morph-lock.toml Added new configuration lock file defining project metadata, coverage, and mappings placeholders.
build/hubspot/erd/target-schema-erd.dbml Added comprehensive DBML schema defining 56 HubSpot-related tables with detailed fields and notes.
build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml Added detailed dbt source configuration YAML for HubSpot tables with metadata and enablement flags.
catalog/hubspot/README.md Added README documenting the auto-generated dbt models and absence of rejected mappings.
catalog/hubspot/airbyte-interop-dbt-project/.gitignore Added .gitignore for dbt project files and directories to exclude build artifacts and logs.
catalog/hubspot/airbyte-interop-dbt-project/dbt_project.yml Added dbt project configuration file specifying models, paths, materialization, and variables.
catalog/hubspot/airbyte-interop-dbt-project/packages.yml Added dbt packages configuration declaring dbt_utils dependency.
catalog/hubspot/airbyte-interop-dbt-project/poe_tasks.toml Added POE tasks configuration file including external task files via environment variable.
catalog/hubspot/airbyte-interop-dbt-project/profiles/profiles.yml Added dbt profiles configuration defining duckdb and motherduck targets with connection details.

Poem

A hop and a skip through the workflow field,
The comment-text carrot is no longer revealed.
With lighter dispatch and inputs trimmed neat,
Our bunny devs bounce to a tidier beat.
🥕✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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.

@aaronsteers
Copy link
Collaborator Author

aaronsteers commented Apr 23, 2025

/poe morph-build hubspot

Error: Unexpected inputs provided: ["comment-text"]

@aaronsteers
Copy link
Collaborator Author

/poe morph-build hubspot

@aaronsteers
Copy link
Collaborator Author

aaronsteers commented Apr 23, 2025

/poe morph-build hubspot

Running poe morph-build hubspot...

Link to job logs.

✅ Poe command morph-build hubspot completed successfully.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml (1)

345-366: Remove trailing spaces to satisfy YAMLlint.
YAMLlint is flagging trailing spaces on multiple lines (e.g., 345, 366, 868, 872–873, 877, 963, 967–968, 972, 1024, 1028–1029, 1033, 1057, 1061–1062, 1066, 1088, 1092–1093, 1097, 1168, 1184, 1282). These extra spaces can cause CI failures.

You can clean them up in bulk with:

sed -i 's/[ \t]*$//' build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml

Or better yet, adjust the morph generator template to trim trailing whitespace on emit.

Also applies to: 868-877, 963-973, 1024-1033, 1057-1066, 1088-1097, 1168-1184, 1282-1282

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 345-345: trailing spaces

(trailing-spaces)


[error] 366-366: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c5fa2d4 and 3612086.

⛔ Files ignored due to path filters (2)
  • build/hubspot/erd/source-schema-erd.svg is excluded by !**/*.svg
  • build/hubspot/erd/target-schema-erd.svg is excluded by !**/*.svg
📒 Files selected for processing (9)
  • build/hubspot/airbyte-interop.morph-lock.toml (1 hunks)
  • build/hubspot/erd/target-schema-erd.dbml (1 hunks)
  • build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml (1 hunks)
  • catalog/hubspot/README.md (1 hunks)
  • catalog/hubspot/airbyte-interop-dbt-project/.gitignore (1 hunks)
  • catalog/hubspot/airbyte-interop-dbt-project/dbt_project.yml (1 hunks)
  • catalog/hubspot/airbyte-interop-dbt-project/packages.yml (1 hunks)
  • catalog/hubspot/airbyte-interop-dbt-project/poe_tasks.toml (1 hunks)
  • catalog/hubspot/airbyte-interop-dbt-project/profiles/profiles.yml (1 hunks)
✅ Files skipped from review due to trivial changes (8)
  • catalog/hubspot/README.md
  • catalog/hubspot/airbyte-interop-dbt-project/packages.yml
  • catalog/hubspot/airbyte-interop-dbt-project/.gitignore
  • catalog/hubspot/airbyte-interop-dbt-project/dbt_project.yml
  • catalog/hubspot/airbyte-interop-dbt-project/profiles/profiles.yml
  • catalog/hubspot/airbyte-interop-dbt-project/poe_tasks.toml
  • build/hubspot/airbyte-interop.morph-lock.toml
  • build/hubspot/erd/target-schema-erd.dbml
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: aaronsteers
PR: airbytehq/airbyte-morph-catalog#95
File: .github/workflows/fix-command.yml:14-17
Timestamp: 2025-04-23T00:05:34.657Z
Learning: GitHub Actions workflows triggered by slash command dispatcher need to declare the `comment-text` input parameter even if they don't explicitly use it, as the dispatcher will fail otherwise.
Learnt from: aaronsteers
PR: airbytehq/airbyte-morph-catalog#95
File: .github/workflows/generate-command.yml:21-24
Timestamp: 2025-04-23T00:05:22.294Z
Learning: Workflows triggered by the slash command dispatcher must declare the `comment-text` input parameter even if they don't use it directly, as the dispatcher will fail if this parameter is not declared in the target workflow.
🪛 YAMLlint (1.35.1)
build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml

[error] 345-345: trailing spaces

(trailing-spaces)


[error] 366-366: trailing spaces

(trailing-spaces)


[error] 868-868: trailing spaces

(trailing-spaces)


[error] 872-872: trailing spaces

(trailing-spaces)


[error] 873-873: trailing spaces

(trailing-spaces)


[error] 877-877: trailing spaces

(trailing-spaces)


[error] 963-963: trailing spaces

(trailing-spaces)


[error] 967-967: trailing spaces

(trailing-spaces)


[error] 968-968: trailing spaces

(trailing-spaces)


[error] 972-972: trailing spaces

(trailing-spaces)


[error] 1024-1024: trailing spaces

(trailing-spaces)


[error] 1028-1028: trailing spaces

(trailing-spaces)


[error] 1029-1029: trailing spaces

(trailing-spaces)


[error] 1033-1033: trailing spaces

(trailing-spaces)


[error] 1057-1057: trailing spaces

(trailing-spaces)


[error] 1061-1061: trailing spaces

(trailing-spaces)


[error] 1062-1062: trailing spaces

(trailing-spaces)


[error] 1066-1066: trailing spaces

(trailing-spaces)


[error] 1088-1088: trailing spaces

(trailing-spaces)


[error] 1092-1092: trailing spaces

(trailing-spaces)


[error] 1093-1093: trailing spaces

(trailing-spaces)


[error] 1097-1097: trailing spaces

(trailing-spaces)


[error] 1168-1168: trailing spaces

(trailing-spaces)


[error] 1184-1184: trailing spaces

(trailing-spaces)


[error] 1282-1282: trailing spaces

(trailing-spaces)

🔇 Additional comments (1)
build/hubspot/requirements/airbyte-interop/src_dbt_requirements.yml (1)

1-4: Note: Auto-generated file – do not manually edit.
This file is produced by the morph CLI (morph generate). Any manual edits here will be overwritten on the next generation cycle. If you need to adjust metadata, descriptions, or column settings, please update the upstream template or configuration in the generator instead of editing this file directly.

@aaronsteers aaronsteers merged commit fa686c1 into main Apr 23, 2025
6 checks passed
@aaronsteers aaronsteers deleted the fix/slash-command-syntaxes branch April 23, 2025 17:57
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.

1 participant