You're reading from Data Engineering with dbt A practical guide to building a cloud-based, pragmatic, and dependable data platform with SQL

Product type Paperback

Published in Jun 2023

Publisher Packt

ISBN-13 9781803246284

Length 578 pages

Edition 1st Edition

Languages

SQL

Tools

dbt

Concepts

Data Engineering

Author (1):

Roberto Zagni

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1: The Foundations of Data Engineering

2. Chapter 1: The Basics of SQL to Transform Data FREE CHAPTER

3. Chapter 2: Setting Up Your dbt Cloud Development Environment

4. Chapter 3: Data Modeling for Data Engineering

5. Chapter 4: Analytics Engineering as the New Core of Data Engineering

6. Chapter 5: Transforming Data with dbt

7. Part 2: Agile Data Engineering with dbt

8. Chapter 6: Writing Maintainable Code

9. Chapter 7: Working with Dimensional Data

10. Chapter 8: Delivering Consistency in Your Data

11. Chapter 9: Delivering Reliability in Your Data

12. Chapter 10: Agile Development

13. Chapter 11: Team Collaboration

14. Part 3: Hands-On Best Practices for Simple, Future-Proof Data Platforms

15. Chapter 12: Deployment, Execution, and Documentation Automation

16. Chapter 13: Moving Beyond the Basics

17. Chapter 14: Enhancing Software Quality

18. Chapter 15: Patterns for Frequent Use Cases

19. Index

Why subscribe?

20. Other Books You May Enjoy

Making your first PR

To complete this chapter, let’s see how we can create a PR in our setup with GitHub as our Git provider.

Remember that you can open a PR only when your working environment is clean – that is, when you have no pending changes after the last commit. Therefore, to create a PR, commit, or revert, all the changes.

Once you have a clean working environment, follow these steps:

To start the process to create a PR on the service provider, click on the Create pull request button.

Figure 11.6: The PR creation option

You will be directed to the site of your Git provider on the page to start the PR creation and confirm the start and target branch. The branches will already be set from the branch you had open in dbt, as main or master. Each Git provider has a slightly different process, but you always have to confirm the start and target branch.