git-remote

To sync local git branches with remote refs safely, fetch the remote state first, then pull with rebase to integrate upstream changes. This avoids merge conflicts by applying local commits on top of the fetched branch history.

Configuring origin and upstream remotes for forks involves adding the upstream repository URL via git commands. This setup allows you to fetch upstream changes independently and push local updates to your origin fork.

Force-with-lease prevents accidental history overwrites during a git push by checking that your local remote refs match the actual remote state. It only allows the push if no one else has updated the remote branch.

Fetching remote state before pushing ensures safe collaborative git workflows by retrieving the latest remote refs without modifying your working directory. You can then rebase local commits and push without overwriting unexpected changes.

Yes, you can automate git fetch, rebase, and push operations using a scripted sync process. The automation detects whether branches are ahead, behind, or diverged, then recommends or performs the appropriate synchronization commands.

Yes, you need git installed as a dependency to manage remote repositories and synchronize local branches. The skill relies on git commands to configure remotes, fetch state, pull with rebase, and push updates.