repository-setup

Name: repository-setup
Availability: InStock
Author: spiriMirror

Configure the upstream remote for forked Git repositories.

307|59|Updated Jun 2, 2024

Search Tags:#git #workflow #repository #remote #forks #upstream

Ready to run

npx skills add https://github.com/spiriMirror/libuipc --skill repository-setup-spirimirror

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repository-setup
Source: https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/repository-setup
Command: npx skills add https://github.com/spiriMirror/libuipc --skill repository-setup-spirimirror

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Working with forked repositories can cause GitHub CLI commands to target the fork rather than the upstream, leading to missed issues and PRs.

Core Features & Use Cases

Adds an upstream remote to ensure commands reference the original repository.
Standardizes remote usage across upstream, fork, and custom remotes to keep workflows consistent.
Use Case: When collaborating across forks, ensure all tooling points to the upstream repository for issues and PRs.

Quick Start

Add upstream as the remote for the upstream repository and verify the remote URL using git remote -v.

Frequently Asked Questions about repository-setup

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

FAQPage Schema

How do I configure upstream remote in a forked git repository?▼

To configure upstream remote in a forked git repository, add the original repository as an upstream remote using git commands. This ensures GitHub CLI commands and tooling reference the upstream repository for issues and PRs rather than the fork.

Why do my GitHub CLI commands target the fork instead of upstream?▼

GitHub CLI commands target the fork instead of upstream because the upstream remote is not configured. Adding an upstream remote resolves fork-related command targeting, ensuring issues and PRs are located in the upstream repository.

What is the best way to standardize remotes across fork and upstream?▼

The best way to standardize remotes across fork and upstream is to apply conventional remote naming practices. Configuring the upstream remote standardizes usage across fork, upstream, and custom remotes to keep workflows consistent.

Do I need to know git remotes to manage multiple repository references?▼

Yes, you need to know git remotes to manage multiple repository references. Configuring upstream remotes requires Git, knowledge of remotes, and conventional remote naming practices to ensure standardized repo references across forks.

Can I verify the upstream remote URL for my forked repository?▼

Yes, you can verify the upstream remote URL for your forked repository by running git remote -v. This command confirms the upstream remote is correctly added and standardized alongside your fork and custom remotes.