Merged
Conversation
* removing incorrect enddocs statement * adding to changelog * Fixing analysis file names to comply with dbt Fusion
fivetran-catfritz
approved these changes
Jul 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Overview
This PR will address the following Issue/Feature: [#167]
This PR will result in the following new package version: 0.20.1
Model renames, but they are analyses.
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fix
quickbooks__balance_sheetandquickbooks__income_statementanalysis models to end in*_analysisto stop duplicate model errors in dbt Fusion, as these are existing end models within the package.Contributors
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps: See ticket
If you had to summarize this PR in an emoji, which would it be?
🏁