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

Feature: Added blog content for "Getting started with git branching strategies and dbt" #6849

Open
wants to merge 11 commits into
base: current
Choose a base branch
from

Conversation

christineberger
Copy link
Contributor

What are you changing in this pull request and why?

Adding a blog post for "Getting started with git Branching Strategies and dbt"
Screenshot 2025-01-29 at 11 25 32 AM

Checklist

  • I have reviewed the Content style guide so my content adheres to these guidelines.
  • [-] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
  • [-] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
  • [-] The content in this PR requires a dbt release note, so I added one to the release notes page.

@christineberger christineberger requested a review from a team as a code owner January 29, 2025 17:25
Copy link

vercel bot commented Jan 29, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview Feb 5, 2025 11:02pm

@christineberger christineberger requested review from joellabes and removed request for a team January 29, 2025 17:26
@github-actions github-actions bot added content Improvements or additions to content developer blog This content fits on the developer blog. size: large This change will more than a week to address and might require more than one person labels Jan 29, 2025
@christineberger
Copy link
Contributor Author

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.

- 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[custom.LatinAbbreviations] Avoid Latin abbreviations: 'that is'. Consider using 'i.e' instead.

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 developer blog This content fits on the developer blog. size: large This change will more than a week to address and might require more than one person
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants