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

[DOCS] Update Add Validation Data or Expectation Suites to a Checkpoint #8931

Merged
merged 27 commits into from Nov 16, 2023

Conversation

kwcanuck
Copy link
Contributor

@kwcanuck kwcanuck commented Nov 3, 2023

In DSB-408, @donaldheppner requested that the topic Add validation data or Expectation suites to a Checkpoint be updated "... to reflect both YAML and Python-style configuration and brought under test". This PR implements these updates.

Definition of done

  • PR title is prefixed with one of: [BUGFIX], [FEATURE], [DOCS], [MAINTENANCE], [CONTRIB]
  • Appropriate tests and docs have been updated

Copy link

netlify bot commented Nov 3, 2023

Deploy Preview for niobium-lead-7998 ready!

Name Link
🔨 Latest commit 3f39ae0
🔍 Latest deploy log https://app.netlify.com/sites/niobium-lead-7998/deploys/65561bb83d7774000818e271
😎 Deploy Preview https://deploy-preview-8931.docs.greatexpectations.io
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot added the devrel This item is being addressed by the Developer Relations Team label Nov 3, 2023
@ghost
Copy link

ghost commented Nov 3, 2023

👇 Click on the image for a new way to code review

Review these changes using an interactive CodeSee Map

Legend

CodeSee Map legend

Copy link
Contributor

@Rachel-Reverie Rachel-Reverie left a comment

Choose a reason for hiding this comment

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

One thing: the PR states that it should include both YAML and python methods for completing the task -- I'm presuming the original description of the PR is outdated, as we've been moving away from YAML based guides (and I didn't see any YAML covered in the updated document or test script). As long as that is the case, then this LGTM.

@kwcanuck kwcanuck added this pull request to the merge queue Nov 16, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 16, 2023
@kwcanuck kwcanuck added this pull request to the merge queue Nov 16, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 16, 2023
@kwcanuck kwcanuck added this pull request to the merge queue Nov 16, 2023
@anthonyburdi anthonyburdi removed this pull request from the merge queue due to a manual request Nov 16, 2023
@anthonyburdi anthonyburdi merged commit f042ad9 into develop Nov 16, 2023
62 checks passed
@anthonyburdi anthonyburdi deleted the validation-update branch November 16, 2023 16:43
@anthonyburdi
Copy link
Member

Force merged after all CI checks passed to enable releasing today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devrel This item is being addressed by the Developer Relations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants