Kedro is a toolbox for production-ready data science. It uses software engineering best practices to help you create data engineering and data science pipelines that are reproducible, maintainable, and modular.
Was leaving suggestions in my review of #3833 and it got a little out of hand 😅
Main aims with these changes:
Give the example nodes names for easier reference, and to be consistent with our recommendations for best practice (this is unfortunately inconsistent across our documentation)
De-technical-ify the explanations as much as possible
Renamed the subsection to fit the format of the rest of the DataCatalog examples
Break up the subsection into more subsubheadings for easier navigation, and because the sidebar seemed to imply only incorrect examples were included:
If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.
Description
Was leaving suggestions in my review of #3833 and it got a little out of hand 😅
Main aims with these changes:
Development notes
Developer Certificate of Origin
We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a
Signed-off-by
line in the commit message. See our wiki for guidance.If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.
Checklist
RELEASE.md
file