tilelang-submodule-pull

Pull tilelang submodules and third-party code with retries and logging.

346|151|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/tile-ai/tilelang-ascend --skill tilelang-submodule-pull
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tilelang-submodule-pull
Source: https://github.com/tile-ai/tilelang-ascend/tree/main/.agents/skills/tilelang-custom-skill/tilelang-submodule-pull
Command: npx skills add https://github.com/tile-ai/tilelang-ascend --skill tilelang-submodule-pull

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Automatically keeps tilelang submodules and third-party code up-to-date, reducing manual sync overhead.

Core Features & Use Cases

  • Scheduled hourly pulls to maintain fresh code across submodules.
  • Automatic error detection and retry logic to recover from transient network failures.
  • Dual pull methods (submodule update --init --recursive and git pull --recurse-submodules) with real-time logging for observability.
  • Use Case: In CI pipelines or local development, ensure submodules stay in sync without manual intervention.

Quick Start

Execute the auto_pull.sh script to start hourly submodule updates and monitor the logs.

Frequently Asked Questions about tilelang-submodule-pull

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

FAQPage Schema
How do I automatically pull git submodules when network failures cause sync drift?

Automating submodule pulls with retry logic handles network instability by detecting errors and executing a 1-hour backoff retry. This script uses submodule update --init --recursive to keep third-party code synced without manual intervention.

What is the best way to keep third-party git submodules up-to-date in a CI pipeline?

Keeping git submodules up-to-date in CI pipelines requires scheduled hourly pulls with real-time logging. This automation script applies dual pull methods to maintain fresh code across submodules, reducing manual sync overhead during development workflows.

Does the automated submodule pull script support recursive updates for nested repositories?

Yes, the automated submodule pull script supports recursive updates for nested repositories. It implements submodule update --init --recursive and git pull --recurse-submodules to ensure nested third-party code stays fully synced.

Why do my git submodules keep falling out of sync and how can I schedule automatic updates?

Git submodules fall out of sync due to submodule drift or transient network failures. You can schedule automatic updates by executing a script that performs hourly pulls with automatic error detection and retry logic to recover missing third-party code.

Can I monitor real-time logs during scheduled git submodule updates?

Yes, you can monitor real-time logs during scheduled git submodule updates. The automation script provides real-time logging for observability, allowing you to track pull methods, error detection, and retry backoff statuses as they execute.