The mismatch guidance told users to re-run 'skillshare init', but init warns and ignores --git-root once a repo already exists, so it never relocates the repo. Reword the CLI message to state the real options: run 'git init' at the new scope dir for a fresh history, or 'mv <old>/.git <new>/.git' to keep history, or set git_root to match the existing repo. Add a 'Changing the scope after init' section to the git_root config reference and point the commit/push/pull pages at it, replacing the same misleading 're-run init' phrasing.
3.2 KiB
sidebar_position
| sidebar_position |
|---|
| 1 |
push
Commit and push source to git remote.
Use commit instead when you only want a local checkpoint without pushing.
skillshare push # Auto-generated message
skillshare push -m "Add pdf" # Custom message
skillshare push --dry-run # Preview
When to Use
- Share skill changes with your other machines via git
- Back up your skills to a remote repository
- After editing skills, commit and push in one command
If you want to save a local checkpoint without sharing it yet, use skillshare commit.
What Happens
flowchart TD
CMD["skillshare push"]
CHECK["1. Check repository status"]
STAGE["2. Stage all changes"]
COMMIT["3. Commit"]
PUSH["4. Push to remote"]
CMD --> CHECK --> STAGE --> COMMIT --> PUSH
Options
| Flag | Description |
|---|---|
-m, --message <msg> |
Commit message (default: "Update skills") |
--dry-run, -n |
Preview without making changes |
Git Root Scope
push operates on the directory selected by the git_root config field (default: skills source). See commit — Git Root Scope for the scope table. If git_root was changed but the git repo still lives in another scope's directory, push prints a "Git root mismatch" error with the exact git init / mv commands to fix it. See Changing the scope after init.
Prerequisites
Your source directory must be a git repository with a remote:
# Set up during init (recommended):
skillshare init --remote git@github.com:you/my-skills.git
# Or add remote to existing setup:
skillshare init --remote git@github.com:you/my-skills.git
Init automatically creates the initial commit, so push works immediately after setup.
First Push Upstream Mapping
On first push (no upstream tracking yet), skillshare push auto-configures upstream:
- If remote already has a default branch (for example
mainortrunk), local changes are pushed to that remote default branch. - If remote is empty, it pushes to your current local branch.
This avoids accidentally creating the wrong remote branch (for example local master while remote uses main).
Examples
# Quick push with auto message
skillshare push
# Custom commit message
skillshare push -m "Add commit-commands skill"
# Preview what would be pushed
skillshare push --dry-run
Conflict Handling
If the remote has newer commits:
$ skillshare push
Push failed
Remote may have newer changes
Run: skillshare pull
Then: skillshare push
Solution:
skillshare pull # Get remote changes
skillshare push # Push your changes
Workflow
Typical workflow for sharing skills:
# 1. Make changes to skills
# 2. Push to remote
skillshare push -m "Update my-skill"
# On another machine:
skillshare pull # Gets changes and syncs
See Also
- commit — Commit locally without pushing
- pull — Pull from remote
- sync — Sync to local targets
- Cross-Machine Sync — Full setup