mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 12:23:22 +00:00
Restructure the entire documentation site following the Diátaxis framework (Learn / How-to / Understand / Reference) with new content across 110 files. ## Information Architecture (M1) - Move all docs to Diátaxis directory structure (learn/, how-to/, understand/, reference/) - Add client-redirects plugin for old URL compatibility - Rewrite sidebar, navbar, and footer to match new IA - Update all internal cross-references ## Homepage + Quickstarts (M2) - Add scenario entry cards to homepage with hand-drawn design - 5 quickstart pages: Claude Code, GitHub Copilot (with copy mode recommendation), Codex, Multiple Tools, Dev Containers, Playground ## Blog + Changelog (M3) - Enable Docusaurus blog plugin with authors.yml - 5 blog posts: 5-min tutorial, managing 50+ skills, skillshare vs vercel/skills comparison, team sharing patterns, write your first skill - Static /changelog page from CHANGELOG.md ## Recipes + Philosophy (M4) - 5 recipe pages: CI/CD validation, enterprise skills, project setup, cross-machine sync, team onboarding - 3 philosophy pages: why-local-first, security-first, sync-modes-explained ## Content Polish - Cross-validate all content against CLI source (19 inaccuracies fixed) - Lowercase "skillshare" throughout (avoid brand conflict with Skillshare Inc.) - Add registry.yaml to file structure and Key Paths docs - Highlight multi-platform git support (GitHub, GitLab, Bitbucket, Gitea, Azure DevOps, AtomGit, Codeberg) - Standardize brew install command - Add AsciinemaPlayer component (cast recordings pending)
112 lines
2.5 KiB
Markdown
112 lines
2.5 KiB
Markdown
---
|
|
sidebar_position: 1
|
|
---
|
|
|
|
# push
|
|
|
|
Commit and push source to git remote.
|
|
|
|
```bash
|
|
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
|
|
|
|
## What Happens
|
|
|
|
```mermaid
|
|
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 |
|
|
|
|
## Prerequisites
|
|
|
|
Your source directory must be a git repository with a remote:
|
|
|
|
```bash
|
|
# 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 `main` or `trunk`), 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
|
|
|
|
```bash
|
|
# 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:
|
|
|
|
```bash
|
|
$ skillshare push
|
|
Push failed
|
|
Remote may have newer changes
|
|
Run: skillshare pull
|
|
Then: skillshare push
|
|
```
|
|
|
|
Solution:
|
|
```bash
|
|
skillshare pull # Get remote changes
|
|
skillshare push # Push your changes
|
|
```
|
|
|
|
## Workflow
|
|
|
|
Typical workflow for sharing skills:
|
|
|
|
```bash
|
|
# 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
|
|
|
|
- [pull](/docs/reference/commands/pull) — Pull from remote
|
|
- [sync](/docs/reference/commands/sync) — Sync to local targets
|
|
- [Cross-Machine Sync](/docs/how-to/sharing/cross-machine-sync) — Full setup
|