git-submit

Automate git-submit CI/CD workflows for Heyo repositories with submodule synchronization.

1|Updated Apr 27, 2026

Search Tags:#automation #git #ci/cd #deployment #submodules #heyo

Ready to run

npx skills add https://github.com/Heyo-Computer/heyo-public --skill git-submit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-submit
Source: https://github.com/Heyo-Computer/heyo-public/tree/main/skills/git-submit
Command: npx skills add https://github.com/Heyo-Computer/heyo-public --skill git-submit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves friction in the Heyo development lifecycle by automating the submission of code branches, managing CI/CD pipeline triggers, and handling complex submodule updates.

Core Features & Use Cases

Automated CI/CD Submission: Orchestrates the patch creation, validation, and merge process for branches against the trunk.
Submodule Management: Ensures gitlink updates are correctly handled during the submission flow to prevent broken dependencies.
Operational Troubleshooting: Provides standardized methods for upgrading the client, re-authenticating sessions, and cleaning up retained VM-backed CI jobs.

Quick Start

Run the git submit command to push your current branch for CI validation and automatic merging.

Frequently Asked Questions about git-submit

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

FAQPage Schema

How do I automate git branch submission for CI/CD pipelines?▼

Automating git branch submission for CI/CD pipelines is done by orchestrating patch creation, validation, and automatic merging against the trunk. This approach triggers pipeline workflows and handles branch submission to streamline code integration and deployment validation.

How do I synchronize git submodules during a deployment workflow?▼

Synchronizing git submodules during a deployment workflow requires ensuring gitlink updates are correctly handled during the submission flow. This prevents broken dependencies and maintains consistency across integrated repository components during CI validation.

Why does my CI/CD job retain VM-backed instances and how do I clean them up?▼

CI/CD jobs may retain VM-backed instances due to incomplete remote job cleanup after deployment validation. Cleaning up these retained VM-backed CI jobs requires standardized operational troubleshooting methods to properly terminate the remote infrastructure sessions.

Do I need local authentication to trigger automated code integration workflows?▼

Local authentication is required to trigger automated code integration workflows. You must authenticate local sessions via heyvm to interact with Heyo-specific infrastructure endpoints for deployment validation and CI/CD pipeline triggers.

What is the best way to re-authenticate sessions for Heyo CI/CD infrastructure endpoints?▼

The best way to re-authenticate sessions for Heyo CI/CD infrastructure endpoints is by using standardized operational troubleshooting methods. Re-authenticating sessions ensures continuous interaction with the defined infrastructure endpoints for code integration.