Column Name mismatch in query_direct_table_access docs

[kirk-dave]

In the query_direct_table_access model there is a mismatch between the docs and the model for table_name.

Happy to contribute a fix for this.

---

dbt-snowflake-monitoring/models/query_direct_table_access.yml

Lines 15 to 16 in 6c440e1

	- name: table_name
	description: Fully qualified table name, i.e. <database_name>.<schema_name>.<table_name>

dbt-snowflake-monitoring/models/query_direct_table_access.sql

Line 6 in 6c440e1

object_name as full_table_name,

[kirk-dave]

If a fix is wanted, let me know what's preferred: table_name or full_table_name

[ian-whitestone]

Thanks @kirkbrunson-dave! A PR would be amazing. Let's update the docs to align with what is already in the model.

Thanks again for flagging.

[kirk-dave]

Great! @ian-whitestone Do I need to do anything to get set up as a contributor? Getting the following pushing the PR to a feature branch

[ian-whitestone]

@kirkbrunson-dave it looks like an issue with your git command

Once you have pushed your commit to your forked repo, you should be able to open a PR from the github UI https://jarv.is/notes/how-to-pull-request-fork-github/