[MAINTENANCE] Make CLI Check-Config and CLI More Robust #3562
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
October 18, 2021 11:35
…ky/update_project_check_config_for_v2_to_v3_migration-2021_10_18-73
…ky/update_project_check_config_for_v2_to_v3_migration-2021_10_18-73
|
✔️ Deploy Preview for niobium-lead-7998 ready! 🔨 Explore the source changes: 1ce810a 🔍 Inspect the deploy log: https://app.netlify.com/sites/niobium-lead-7998/deploys/616e006f8525c7000781c5ef 😎 Browse the preview: https://deploy-preview-3562--niobium-lead-7998.netlify.app |
HOWDY! This is your friendly 🤖 CHANGELOG bot 🤖Please don't forget to add a clear and succinct description of your change under the Develop header in ✨ Thank you! ✨ |
| @@ -22,4 +22,4 @@ ruamel.yaml>=0.16 # package | |||
| scipy>=0.19.0 # package | |||
| termcolor>=1.1.0 # package | |||
| tqdm>=4.59.0 | |||
| tzlocal>=1.2 # package | |||
| tzlocal==3.0 # package | |||
Shinnnyshinshin
approved these changes
Oct 18, 2021
alexsherstinsky
deleted the
feature/GREAT-200/GREAT-303/alexsherstinsky/update_project_check_config_for_v2_to_v3_migration-2021_10_18-73
branch
Shinnnyshinshin
pushed a commit
that referenced
this pull request
Oct 21, 2021
…reat-expectations/great_expectations into docs/GREAT-302/migration-guide * 'docs/GREAT-302/migration-guide' of https://github.com/great-expectations/great_expectations: (27 commits) [FEATURE] Migration of Expectations to Atomic Prescriptive Renderers part 1 (#3530) [DOCS]Minor Friction (#3574) CLOUD-99: Editing Expectation Suites programmatically (#3564) fix link to expectation glossary (#3558) [BUGFIX] SQLAlchemy version 1.3.24 compatibility in map metric provider (#3507) [DOCS] Removed duplicate prereq, how_to_instantiate_a_data_context_without_a_yml_file.md (#3481) better version control (#3565) [MAINTENANCE] Make CLI Check-Config and CLI More Robust (#3562) Update contributing_checklist.md (#3518) [DOCS] How to introspect and partition an SQL database (#3465) Docs/simplify getting started (#3555) Update contributing.md (#3524) Update contributing.md (#3523) Docs/revamp style guides (#3554) Update contributing_test.md (#3519) Update contributing_style.md (#3521) [DOCS] Improved installation instructions, included in-line installation instructions to getting started (#3509) Update how_to_configure_a_new_data_context_with_the_cli.md (#3556) typo in documentation (#3542) update expect_column_values_to_be_us_zipcode_within_radius_of_given_zipcode requirements ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please annotate your PR title to describe what the PR does, then give a brief bulleted description of your PR below. PR titles should begin with [BUGFIX], [FEATURE], [DOCS], or [MAINTENANCE]. If a new feature introduces breaking changes for the Great Expectations API or configuration files, please also add [BREAKING]. You can read about the tags in our contributor checklist.
Changes proposed in this pull request:
After submitting your PR, CI checks will run and @tiny-tim-bot will check for your CLA signature.
For a PR with nontrivial changes, we review with both design-centric and code-centric lenses.
In a design review, we aim to ensure that the PR is consistent with our relationship to the open source community, with our software architecture and abstractions, and with our users' needs and expectations. That review often starts well before a PR, for example in github issues or slack, so please link to relevant conversations in notes below to help reviewers understand and approve your PR more quickly (e.g.
closes #123).Previous Design Review notes:
Definition of Done
Please delete options that are not relevant.
Thank you for submitting!