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.

Sign up for GitHub

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

Jump to bottom

Typo in `defer-env-id` #4337

Closed

bthomson22 opened this issue Oct 26, 2023 · 0 comments

Contributor

bthomson22 commented Oct 26, 2023

docs.getdbt.com/website/docs/docs/cloud/about-cloud-develop-defer.md

Lines 42 to 52 in 7484d0b

    
           dever-env-id: '123456' 
        
           ``` 
        
           </File> 
        
           <File name="dbt_project.yml">  
        
           ```yml 
        
           dbt_cloud: 
        
             dever-env-id: '123456'

Noticed in our product docs for Cloud CLI we use dever-env-id in the code blocks, while the description above has defer-env-id.

The text was updated successfully, but these errors were encountered:

bthomson22 mentioned this issue

Fix: Updated dever-env-id to defer-env-id in Cloud CLI docs #4338

Merged

7 tasks

mirnawong1 added a commit that referenced this issue


          Fix: Updated dever-env-id to defer-env-id in Cloud CLI docs (#4338)

efbc769

## What are you changing in this pull request and why?
<!---
Describe your changes and why you're making them. If linked to an open
issue or a pull request on dbt Core, then link to them here! 

To learn more about the writing conventions used in the dbt Labs docs,
see the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md).
-->

Ref issue: #4337

This PR fixes a typo in our Cloud CLI docs, updating `dever-env-id` to
`defer-env-id`.


![image](https://github.com/dbt-labs/docs.getdbt.com/assets/16456253/e94a78c2-fc31-4742-97ad-ed4b4e8ebfcc)

Straightforward :)

I admittedly have not tested this, and I'm not even sure how - but
hoping this is straightforward and perhaps doesn't require versioning?

## Checklist
<!--
Uncomment if you're publishing docs for a prerelease version of dbt
(delete if not applicable):
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
-->
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):
- [ ] Add page to `website/sidebars.js`
- [ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):
- [ ] Remove page from `website/sidebars.js`
- [ ] Add an entry `website/static/_redirects`
- [ ] [Ran link
testing](https://github.com/dbt-labs/docs.getdbt.com#running-the-cypress-tests-locally)
to update the links that point to the deleted page

mirnawong1 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment