Feature: Added blog content for "Getting started with git branching strategies and dbt" #6849
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
christineberger
requested review from
joellabes
and removed request for
a team
github-actions
bot
added
content
christineberger
requested review from
jasnonaz,
Stevedow99,
T-Dunlap and
cohms
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Hey all! Let me know what else I need to do here - would appreciate a last look-over from @cohms @T-Dunlap and @Stevedow99. Joel has read through the rough draft in Notion. |
…cesses and Environments"
| - pull requests must have at least 1 reviewer's approval | ||
| - **A PR template** ([such as our boiler-plate PR template](https://docs.getdbt.com/blog/analytics-pull-request-template)) for `feature` PRs against `main` | ||
|
|
||
| ### dbt Cloud processes and environments |
There was a problem hiding this comment.
[custom.SentenceCaseHeaders] 'dbt Cloud processes and environments' should use sentence-style capitalization. Try 'dbt cloud processes and environments' instead.
|
|
||
| <Lightbox src="img/blog/2025-01-28-git-branching-strategies-and-dbt/13_more_branches.png" title="A git strategy with more branches" width="85%" /> | ||
|
|
||
| This structure is mostly desired when there are requirements for using different versions data (i.e scrubbed data) by different teams, but working with the same code changes. This structure allows each team to have a dedicated environment for deployments. Example: |
There was a problem hiding this comment.
[custom.Typos] Oops there's a typo -- did you really mean 'i.e'?
|
|
||
| <Lightbox src="img/blog/2025-01-28-git-branching-strategies-and-dbt/13_more_branches.png" title="A git strategy with more branches" width="85%" /> | ||
|
|
||
| This structure is mostly desired when there are requirements for using different versions data (i.e scrubbed data) by different teams, but working with the same code changes. This structure allows each team to have a dedicated environment for deployments. Example: |
There was a problem hiding this comment.
[custom.LatinAbbreviations] Avoid Latin abbreviations: 'that is'. Consider using 'i.e' instead.
|
|
||
| <Lightbox src="img/blog/2025-01-28-git-branching-strategies-and-dbt/13_more_branches.png" title="A git strategy with more branches" width="85%" /> | ||
|
|
||
| This structure is mostly desired when there are requirements for using different versions data (i.e scrubbed data) by different teams, but working with the same code changes. This structure allows each team to have a dedicated environment for deployments. Example\: |
There was a problem hiding this comment.
[custom.LatinAbbreviations] Avoid Latin abbreviations: 'that is'. Consider using 'i.e' instead.
|
|
||
| <Lightbox src="img/blog/2025-01-28-git-branching-strategies-and-dbt/13_more_branches.png" title="A git strategy with more branches" width="85%" /> | ||
|
|
||
| This structure is mostly desired when there are requirements for using different versions data (i.e scrubbed data) by different teams, but working with the same code changes. This structure allows each team to have a dedicated environment for deployments. Example\: |
There was a problem hiding this comment.
[custom.Typos] Oops there's a typo -- did you really mean 'i.e'?
| - Development\: Switch your environment to use the **custom branch** option and specify your new middle branch’s name. This will base developers off of the middle branch. | ||
| - Continous Integration\: If you have an existing environment for this, ensure the **custom branch** is also changed to the middle branch’s name. This will change the CI job’s trigger to occur on pull requests to your middle branch. | ||
|
|
||
| **At this point, your developers will be following the indirect promotion workflow and you can continue working on things in the background.** You may still need to set up a database, database permissions, environments, deployment jobs, etc. Here is a short checklist to help you out! Refer back to our section on indirect promotion for many more details\: |
There was a problem hiding this comment.
[custom.LatinAbbreviations] Avoid Latin abbreviations: 'and so on'. Consider using 'etc' instead.
|
|
||
| Here’s our branching strategy again, but now with the dbt Cloud processes we want to incorporate\: | ||
|
|
||
| <Lightbox src="img/blog/2025-01-28-git-branching-strategies-and-dbt/3_direct_dbt_deployment.png" title="Direct Promotion strategy with dbt cloud processes denoted" width="85%" /> |
There was a problem hiding this comment.
@christineberger this one needs a forward slash in front of img
There was a problem hiding this comment.
And same for the rest of the images below in this file. It looks like they just need that forward slash on the image src and they should be good to go!
There was a problem hiding this comment.
Thank you! I'll try this out ❤️
What are you changing in this pull request and why?
Adding a blog post for "Getting started with git Branching Strategies and dbt"
Checklist