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

Add most recent dbt-docs changes #10307

Merged
merged 3 commits into from
Jun 14, 2024

Conversation

FishtownBuildBot
Copy link
Collaborator

Auto generated changes from generate-docs-for-dbt-core.yml workflow

@FishtownBuildBot FishtownBuildBot requested a review from a team as a code owner June 13, 2024 14:49
@FishtownBuildBot FishtownBuildBot added the dbt-docs [dbt feature] documentation site, powered by metadata artifacts label Jun 13, 2024
@cla-bot cla-bot bot added the cla:yes label Jun 13, 2024
@github-actions github-actions bot added the community This PR is from a community member label Jun 13, 2024
Copy link

codecov bot commented Jun 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.71%. Comparing base (d4a6482) to head (be45638).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #10307      +/-   ##
==========================================
- Coverage   88.74%   88.71%   -0.04%     
==========================================
  Files         180      180              
  Lines       22483    22483              
==========================================
- Hits        19953    19946       -7     
- Misses       2530     2537       +7     
Flag Coverage Δ
integration 85.97% <ø> (-0.10%) ⬇️
unit 61.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@MichelleArk
Copy link
Contributor

Sanity checking - these changes are covered by the 🎩 done in dbt-labs/dbt-docs#513, right @aranke ?

@aranke
Copy link
Member

aranke commented Jun 13, 2024

Sanity checking - these changes are covered by the 🎩 done in dbt-labs/dbt-docs#513, right @aranke?

Yes, correct. I technically ran this workflow off dbt-labs/dbt-docs#514, but is identical to changes from dbt-labs/dbt-docs#513

@aranke aranke merged commit 8ee8b25 into main Jun 14, 2024
63 checks passed
@aranke aranke deleted the dbt-docs-release/20240613-144120_9501729434 branch June 14, 2024 15:29
Copy link
Contributor

The backport to 1.7.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-10307-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8ee8b2560a1ff05f2451855cc6c9c93aa6388309
# Push it to GitHub
git push --set-upstream origin backport-10307-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest

Then, create a pull request where the base branch is 1.7.latest and the compare/head branch is backport-10307-to-1.7.latest.

github-actions bot pushed a commit that referenced this pull request Jun 17, 2024
Co-authored-by: Kshitij Aranke <kshitij.aranke@dbtlabs.com>
(cherry picked from commit 8ee8b25)
Copy link
Contributor

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-10307-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8ee8b2560a1ff05f2451855cc6c9c93aa6388309
# Push it to GitHub
git push --set-upstream origin backport-10307-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-10307-to-1.6.latest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 1.6.latest backport 1.7.latest backport 1.8.latest cla:yes community This PR is from a community member dbt-docs [dbt feature] documentation site, powered by metadata artifacts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants