Skip to content

[DOCS] expectation details in asset history#11814

Open
klavavej wants to merge 3 commits into
developfrom
kml/GX-3135/editsInAssetHistory
Open

[DOCS] expectation details in asset history#11814
klavavej wants to merge 3 commits into
developfrom
kml/GX-3135/editsInAssetHistory

Conversation

@klavavej
Copy link
Copy Markdown
Contributor

Docs in support of https://greatexpectations.atlassian.net/browse/GX-3135

  • Description of PR changes above includes a link to an existing GitHub issue
  • PR title is prefixed with one of: [BUGFIX], [FEATURE], [DOCS], [MAINTENANCE], [CONTRIB], [MINORBUMP]
  • Code is linted - run invoke lint (uses ruff format + ruff check)
  • Appropriate tests and docs have been updated

For more information about contributing, visit our community resources.

After you submit your PR, keep the page open and monitor the statuses of the various checks made by our continuous integration process at the bottom of the page. Please fix any issues that come up and reach out on Slack if you need help. Thanks for contributing!

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 14, 2026

Deploy Preview for niobium-lead-7998 ready!

Name Link
🔨 Latest commit 5de678d
🔍 Latest deploy log https://app.netlify.com/projects/niobium-lead-7998/deploys/69dea60a7b89610008811a1f
😎 Deploy Preview https://deploy-preview-11814.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 project configuration.

@klavavej klavavej marked this pull request as ready for review April 14, 2026 20:39
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates GX Cloud documentation to better describe how Expectation change details appear in Data Asset history and how to navigate between Expectation history and Data Asset history.

Changes:

  • Clarifies that Data Asset history includes added/edited/removed Expectation events.
  • Refines cross-links between “Expectation history” and “Data Asset history” sections for better navigation.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
docs/docusaurus/docs/cloud/expectations/manage_expectations.md Adjusts the “deleted Expectations” tip text linking to Data Asset history.
docs/docusaurus/docs/cloud/data_assets/manage_data_assets.md Updates Data Asset history description and refines the tip linking back to Expectation history.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

## View Data Asset history

For an audit trail of who added or removed which Expectations and when, visit a Data Asset’s **History** tab.
For an audit trail of who added, edited, or removed which Expectations and when, visit a Data Asset’s **History** tab.
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

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

Wording is a bit ungrammatical: “removed which Expectations” is awkward. Consider rephrasing to “who added, edited, or removed Expectations, and when” (or similar) for readability.

Suggested change
For an audit trail of who added, edited, or removed which Expectations and when, visit a Data Asset’s **History** tab.
For an audit trail of who added, edited, or removed Expectations, and when, visit a Data Asset’s **History** tab.

Copilot uses AI. Check for mistakes.

:::tip Looking for deleted Expectations?
For an audit trail of who removed which Expectations and when, [view Data Asset history](/cloud/data_assets/manage_data_assets.md#view-data-asset-history).
For an audit trail of who added, edited, or removed a deleted Expectation and when, [view Data Asset history](/cloud/data_assets/manage_data_assets.md#view-data-asset-history).
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

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

The phrase “removed a deleted Expectation” reads as contradictory/unclear (an Expectation can be deleted/removed, but not “removed” after it’s already deleted). Suggest rewording to something like “added, edited, or deleted an Expectation” (or “added, edited, or removed an Expectation”) to clearly describe the actions captured in Data Asset history.

Suggested change
For an audit trail of who added, edited, or removed a deleted Expectation and when, [view Data Asset history](/cloud/data_assets/manage_data_assets.md#view-data-asset-history).
For an audit trail of who added, edited, or deleted an Expectation and when, [view Data Asset history](/cloud/data_assets/manage_data_assets.md#view-data-asset-history).

Copilot uses AI. Check for mistakes.
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 14, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.49%. Comparing base (ac33e6d) to head (5de678d).
⚠️ Report is 44 commits behind head on develop.

❗ There is a different number of reports uploaded between BASE (ac33e6d) and HEAD (5de678d). Click for more details.

HEAD has 72 uploads less than BASE
Flag BASE (ac33e6d) HEAD (5de678d)
3.11 2 0
3.13 2 0
3.10 2 0
3.12 2 0
3.13 athena 2 0
3.13 clickhouse 2 0
3.13 big 2 0
3.13 aws_deps 2 0
3.13 mysql 2 0
3.13 spark_connect 2 0
3.13 openpyxl or pyarrow or project or sqlite or aws_creds 2 0
3.13 sql_server 2 0
3.13 filesystem 2 0
3.13 postgresql 2 0
cloud 2 0
3.13 trino 2 0
3.13 spark 2 0
3.13 bigquery 1 0
3.13 databricks 1 0
3.13 gx-redshift 1 0
3.13 snowflake 1 0
3.11 athena 1 0
3.12 athena 1 0
3.12 aws_deps 1 0
3.11 aws_deps 1 0
3.10 athena 1 0
3.11 clickhouse 1 0
3.10 clickhouse 1 0
3.10 aws_deps 1 0
3.11 big 1 0
3.12 big 1 0
3.10 big 1 0
3.11 mysql 1 0
3.12 openpyxl or pyarrow or project or sqlite or aws_creds 1 0
3.10 spark_connect 1 0
3.11 openpyxl or pyarrow or project or sqlite or aws_creds 1 0
3.10 mysql 1 0
3.12 mysql 1 0
3.12 spark_connect 1 0
3.10 openpyxl or pyarrow or project or sqlite or aws_creds 1 0
3.11 sql_server 1 0
3.11 postgresql 1 0
3.11 spark_connect 1 0
3.12 filesystem 1 0
3.10 sql_server 1 0
3.10 filesystem 1 0
3.11 filesystem 1 0
3.12 postgresql 1 0
3.12 sql_server 1 0
3.10 postgresql 1 0
3.10 trino 1 0
3.12 trino 1 0
3.11 trino 1 0
3.11 spark 1 0
3.12 spark 1 0
Additional details and impacted files
@@             Coverage Diff              @@
##           develop   #11814       +/-   ##
============================================
- Coverage    84.67%   63.49%   -21.18%     
============================================
  Files          471      469        -2     
  Lines        39179    39177        -2     
============================================
- Hits         33174    24877     -8297     
- Misses        6005    14300     +8295     
Flag Coverage Δ
3.10 ?
3.10 athena ?
3.10 aws_deps ?
3.10 big ?
3.10 clickhouse ?
3.10 filesystem ?
3.10 mysql ?
3.10 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.10 postgresql ?
3.10 spark_connect ?
3.10 sql_server ?
3.10 trino ?
3.11 ?
3.11 athena ?
3.11 aws_deps ?
3.11 big ?
3.11 clickhouse ?
3.11 filesystem ?
3.11 mysql ?
3.11 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.11 postgresql ?
3.11 spark ?
3.11 spark_connect ?
3.11 sql_server ?
3.11 trino ?
3.12 ?
3.12 athena ?
3.12 aws_deps ?
3.12 big ?
3.12 filesystem ?
3.12 mysql ?
3.12 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.12 postgresql ?
3.12 spark ?
3.12 spark_connect ?
3.12 sql_server ?
3.12 trino ?
3.13 ?
3.13 athena ?
3.13 aws_deps ?
3.13 big ?
3.13 bigquery ?
3.13 clickhouse ?
3.13 databricks ?
3.13 filesystem ?
3.13 gx-redshift ?
3.13 mysql ?
3.13 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.13 postgresql ?
3.13 snowflake ?
3.13 spark ?
3.13 spark_connect ?
3.13 sql_server ?
3.13 trino ?
cloud ?
docs-basic 59.51% <ø> (ø)
docs-creds-needed 58.11% <ø> (ø)
docs-spark 57.56% <ø> (ø)

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.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants