Add tripleaceme/dbt-doc-inherit

[tripleaceme]

Description

Adds tripleaceme/dbt-doc-inherit to the dbt package hub.

dbt-doc-inherit propagates column descriptions along the DAG — define once, inherit downstream. It reduces documentation effort by automatically passing descriptions from upstream models to downstream ones.

Link to your package's repository: https://github.com/tripleaceme/dbt-doc-inherit

Checklist

First run experience

• (Required): The package includes a licence file detectable by GitHub.
• The package includes a README which explains how to get started with the package and customise its behaviour
• The README indicates which data warehouses/platforms are expected to work with this package

Customisability

• The package uses ref or source, instead of hard-coding table references.

Dependencies

Dependencies on dbt Core

• The package has set a supported require-dbt-version range in dbt_project.yml: [">=1.6.0", "<2.0.0"]

Dependencies on other packages defined in packages.yml:

• Dependencies are imported from the dbt Package Hub when available, as opposed to a git installation.
• Dependencies contain the widest possible range of supported versions, to minimise issues in dependency resolution.
• In particular, dependencies are not pinned to a patch version unless there is a known incompatibility.

Interoperability

• The package does not override dbt Core behaviour in such a way as to impact other dbt resources not provided by the package.
• The package uses the cross-database macros built into dbt Core where available.
• The package disambiguates its resource names to avoid clashes with nodes that are likely to already exist in a project.

Versioning

• (Required): The package's git tags validates against the regex defined in hubcap/version.py.
• The package's version follows the guidance of Semantic Versioning 2.0.0.

[dbeatty10]

Love it @tripleaceme (and also love that your github handle goes with your name 💡 )

Please add this checklist to the PR description and fill it out -- it's a requirement we have for all new packages going in to the hub.

[tripleaceme]

Love it @tripleaceme (and also love that your github handle goes with your name 💡 )

Please add this checklist to the PR description and fill it out -- it's a requirement we have for all new packages going in to the hub.

Thank you @dbeatty10

Adding the information required.

[dbeatty10]

🚀

[tripleaceme]

🚀

Fixed the conflicts issue.