datalad-push

Push saved DataLad dataset state to a configured remote.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/bcmcpher/my-skills --skill datalad-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datalad-push
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/datalad-cli/skills/datalad-push
Command: npx skills add https://github.com/bcmcpher/my-skills --skill datalad-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push saved DataLad dataset state from a local repository to a configured remote to publish changes and share data.

Core Features & Use Cases

  • Transfers annexed data and git history in a controlled order honoring publish dependencies.
  • Supports selecting a target remote, optional data modes, and recursive subdataset pushes.
  • Use Case: You want to publish a dataset to a storage host and make the history available to collaborators.

Quick Start

Push the current DataLad dataset state to a configured remote after validating the dataset and staging changes.

Frequently Asked Questions about datalad-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push a DataLad dataset to a configured remote?

To push a DataLad dataset, you need a clean working tree and a configured remote. The process validates the dataset context, identifies the target remote, and executes the datalad push command to transfer annexed data and git history safely.

What's the best way to transfer annexed data and git history to a remote repository?

Transferring annexed data and git history requires a controlled order that honors publish-depends configurations. This ensures the dataset state is correctly pushed to the remote, making data and history available for collaborators.

Can I recursively push DataLad subdatasets to a remote?

Yes, you can recursively push DataLad subdatasets by enabling the -r recursion flag. This allows the push operation to include nested subdatasets, ensuring the entire dataset hierarchy is published.

Does the DataLad push process require a clean working tree?

Yes, a clean working tree is required. The process validates the DataLad context and checks for uncommitted changes to ensure only saved dataset state is pushed to the configured remote.

How do data modes work when publishing a DataLad dataset?

Data modes control how annexed data is transferred during a DataLad push. By supporting specific --data modes, the push operation manages the transfer of file contents to the remote alongside the git history.