data-versioning
Here are 24 public repositories matching this topic...
Description
We're running usability tests and would love for you to record walking through our tutorials. The idea for this ticket is that you do a screen capture walking through one of more of the following examples:
- Hello World! (15 minutes)
- [Iris Dataset](https://kedro.readthedocs.io/en/stable/02_get_started
-
Updated
Feb 23, 2022 - Python
Documentation around storage namespace should be improved:
- Stress that the storage namespace should be empty for a new repository. The reason for this is that repo-level settings would be overwritten if two repositories used the same storage namespace (you don't necessarily have to mention the
reason).
An exception for this is bare repositories which may be created over an existing, alr
-
Updated
Feb 23, 2022 - Jupyter Notebook
-
Updated
Feb 11, 2022 - JavaScript
-
Updated
Feb 18, 2022 - Python
-
Updated
Feb 22, 2022 - Python
-
Updated
Jul 3, 2019
-
Updated
Feb 13, 2022 - R
-
Updated
Jan 21, 2022 - Jupyter Notebook
-
Updated
Feb 1, 2022 - Python
While API action names have been renamed to refer to tag, there are some cases where parameter names and returned struct keys still refer to version.
Examples:
- in
resource_show_tag:version_idparameter,version_metadatain the returned dict - Same in
package_show_tag
-
Updated
Jan 6, 2021
-
Updated
Feb 23, 2022 - Go
-
Updated
Dec 21, 2021 - Java
-
Updated
Jul 28, 2021 - Jupyter Notebook
-
Updated
Aug 1, 2021 - HTML
-
Updated
Oct 4, 2021 - Python
-
Updated
Feb 12, 2020
-
Updated
Feb 17, 2022 - JavaScript
-
Updated
Mar 22, 2020 - TypeScript
Improve this page
Add a description, image, and links to the data-versioning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the data-versioning topic, visit your repo's landing page and select "manage topics."
Can't use 'Comment' as column alias.
To reproduce: