Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Core] Add PR checklist item for dbt Cloud release notes #6245

Closed
1 task done
dbeatty10 opened this issue Oct 4, 2024 · 0 comments · Fixed by #6323
Closed
1 task done

[Core] Add PR checklist item for dbt Cloud release notes #6245

dbeatty10 opened this issue Oct 4, 2024 · 0 comments · Fixed by #6323
Assignees
Labels
content Improvements or additions to content dbt-core v1.9 improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@dbeatty10
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://github.com/dbt-labs/docs.getdbt.com/blob/715bf777fe03d10b0b514cb3b0c56340fe8728e6/.github/pull_request_template.md

What part(s) of the page would you like to see updated?

Add PR checklist item for dbt Cloud release notes (for applicable PRs -- probs commented out by default).

Additional information

No response

@dbeatty10 dbeatty10 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear dbt-core v1.9 labels Oct 4, 2024
@runleonarun runleonarun changed the title Add PR checklist item for dbt Cloud release notes [Core] Add PR checklist item for dbt Cloud release notes Oct 15, 2024
@runleonarun runleonarun self-assigned this Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content dbt-core v1.9 improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants