From 33ee48f5b7b3f289281d7e1ea7e646a0883bff9e Mon Sep 17 00:00:00 2001 From: Pablo Martin Date: Wed, 6 Mar 2024 11:21:11 +0100 Subject: [PATCH] some changes in branching strategy --- .../branches/models.md} | 0 README.md | 4 +++- 2 files changed, 3 insertions(+), 1 deletion(-) rename .azuredevops/{pull_request_template.md => pull_request_template/branches/models.md} (100%) diff --git a/.azuredevops/pull_request_template.md b/.azuredevops/pull_request_template/branches/models.md similarity index 100% rename from .azuredevops/pull_request_template.md rename to .azuredevops/pull_request_template/branches/models.md diff --git a/README.md b/README.md index 65e789d..152650e 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,9 @@ pg_restore -h localhost -U postgres -W -d dwh core.dump This repo works in a trunk-based-development philosophy (). -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