-
Notifications
You must be signed in to change notification settings - Fork 947
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
Ensure learners don't try to save a new file in main branch #4304
Ensure learners don't try to save a new file in main branch #4304
Conversation
Updated instructions to ensure that the learners don't struggle with creating new files in the main branch.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -88,7 +88,7 @@ In order to let dbt connect to your warehouse, you'll need to generate a keyfile | |||
4. Click **Upload a Service Account JSON File** in settings. | |||
5. Select the JSON file you downloaded in [Generate BigQuery credentials](#generate-bigquery-credentials) and dbt Cloud will fill in all the necessary fields. | |||
6. Click **Test Connection**. This verifies that dbt Cloud can access your BigQuery account. | |||
7. Click **Next** if the test succeeded. If it failed, you might need to go back and regenerate your BigQuery credentials. | |||
7. Click **Next** if the test succeeded. If it fails, you might need to go back and regenerate your BigQuery credentials. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammatical Error Correction.
@@ -100,13 +100,10 @@ Now that you have a repository configured, you can initialize your project and s | |||
|
|||
1. Click **Start developing in the IDE**. It might take a few minutes for your project to spin up for the first time as it establishes your git connection, clones your repo, and tests the connection to the warehouse. | |||
2. Above the file tree to the left, click **Initialize dbt project**. This builds out your folder structure with example models. | |||
3. Make your initial commit by clicking **Commit and sync**. Use the commit message `initial commit` and click **Commit**. This creates the first commit to your managed repo and allows you to open a branch where you can add new dbt code. | |||
3. Make your initial commit by clicking **Commit and sync**. Use the commit message `initial commit` and click **Commit**. This creates the first commit to your managed repo and allows you to open a branch where you can add a new dbt code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammatical error Fix.
4. You can now directly query data from your warehouse and execute `dbt run`. You can try this out now: | ||
- Click **+ Create new file**, add this query to the new file, and click **Save as** to save the new file: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressing the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anksu2024 Removing this might muddle the instructions. Would it be better to direct the customer to put this on a different branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I followed the instructions and the same thing we are doing in the next section. i.e. we create a new branch and our first model on the branch. Hence, it would be a redundant activity, and the learner's flow would become more streamlined with this change.
As a learner myself, I struggled for some time with this. Hence, I thought of adding.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matthewshaver : Following up on this. Thx.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anksu2024 Thank you for that perspective. I agree with the changes, but we must make some more adjustments to this section due to removing the text. I'll merge directly here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind! I see you added it, Thank you!
…file_in_main_branch
…file_in_main_branch
Updated the heading to reflect what the section does.
|
||
|
||
## Set up a dbt Cloud managed repository | ||
<Snippet path="tutorial-managed-repo" /> | ||
|
||
|
||
## Initialize your dbt project and start developing | ||
## Initialize your dbt project |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing this from here because we are starting development next section onwards.
We are making this section straightforward to follow.
…file_in_main_branch
…file_in_main_branch
Approved! Will inspect the final preview once it's ready and then merge. Thank you @anksu2024 ! |
Updated instructions to ensure that the learners don't struggle with creating new files in the main branch.
Resolves #4289
What are you changing in this pull request and why?
While trying the dbt BigQuery Quickstart I struggled with the instructions around creating and saving new file.
Because I was in the main branch, I could not save a new file.
And unless I save it, DBT doesn't materialize it as a table when we do
dbt run
So, there is no point in creating a new file in this section, when we are already doing that in the next section.
This change with prevent confusion for the learner.
Also, we are creating a new branch and a new file in the next section. So the things will be clearer.
Checklist
dbt cloud
UI.