The PR template of dbt-utils has a single section for the main body of the description:
Description & motivation
But dbt-core, dbt-adapters, etc. have two sections:
Problem
Solution
The latter allows the contributor to separate the design decisions of the implementation from the problem that it is trying to solve. This makes it easier for the contributor to write the PR description. It also makes it easier for others to read (code reviewers, users, etc.)
Solution
Adopt the standard established by dbt-core, dbt-adapters, etc in order to make it easier to read/write and also for those working across repos.
resolves #910
Problem
The PR template of dbt-utils has a single section for the main body of the description:
But dbt-core, dbt-adapters, etc. have two sections:
The latter allows the contributor to separate the design decisions of the implementation from the problem that it is trying to solve. This makes it easier for the contributor to write the PR description. It also makes it easier for others to read (code reviewers, users, etc.)
Solution
Adopt the standard established by dbt-core, dbt-adapters, etc in order to make it easier to read/write and also for those working across repos.
Checklist