You're correct about the repositories, and there's a bit of confusion that often happens with Elementary's repositories. Elementary has two separate repositories: 1. The dbt package repository: [dbt-data-reliability](https://github.com/elementary-data/dbt-data-reliability) - This is the repository for the Elementary dbt package that you reference in your packages.yml - When you specify

package: elementary-data/elementary

in your packages.yml, this is the actual repository being used 2. The CLI/Python package repository: [elementary](https://github.com/elementary-data/elementary) - This contains the code for the Elementary CLI tool and Python package - This is installed via pip, not through dbt packages This separation sometimes causes confusion, as noted in several community discussions. For example, when someone tried to install version 0.16.1 of the dbt package but found it wasn't available, it was because 0.16.1 was a CLI version while the dbt package was at 0.16.0 [as explained in this GitHub issue](https://github.com/elementary-data/elementary/issues/1670). The Elementary team has acknowledged this can be confusing, as seen in their [contributions documentation](https://docs.elementary-data.com/oss/general/contributions) where they clearly state that "Elementary code is separated into two repositories." When installing the dbt package via git instead of hub.getdbt.com, you would use:

yaml - git: "<https://github.com/elementary-data/dbt-data-reliability.git>"   revision: your-version-here

As confirmed by Elementary team members in [this Slack conversation](https://slack.com/archives/C02CTC89LAX/p1676595374183909). Is there anything specific you're trying to accomplish with Elementary that I can help with?