some changes in branching strategy
This commit is contained in:
parent
e256635cbe
commit
33ee48f5b7
2 changed files with 3 additions and 1 deletions
|
|
@ -47,7 +47,9 @@ pg_restore -h localhost -U postgres -W -d dwh core.dump
|
||||||
|
|
||||||
This repo works in a trunk-based-development philosophy (<https://trunkbaseddevelopment.com/>).
|
This repo works in a trunk-based-development philosophy (<https://trunkbaseddevelopment.com/>).
|
||||||
|
|
||||||
Open a feature branch (`feature/your-branch-name`) for any changes and make it short-lived. It's fine and encouraged to build incrementally towards a `mart` level table with multiple PRs as long as you keep the model buildable along the way.
|
When working on Data modeling stuff (models, sources, seeds, docs, etc.) use a `models` branch (i.e. `models/churned-users`). It's fine and encouraged to build incrementally towards a `reporting` level table with multiple PRs as long as you keep the model buildable along the way.
|
||||||
|
|
||||||
|
For other matters, use a `chores` branch (i.e. `chores/add-dbt-package`).
|
||||||
|
|
||||||
## Project organization
|
## Project organization
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue