STG-PULL(1)

📦
version 2.7.0 · 9 versions
, in opensuse-leap 16.0

💅 STG-PULL(1) — the StGit manual, bestie edition 🎀

okay so we're doing stg-pull today, from the StGit manual, and honestly? it's giving "glow-up for your patch stack" ✨

🌸 NAME 🌸

stg-pull — pull changes from a remote repository 🫶

🦋 SYNOPSIS 🦋

stg pull [OPTIONS] [repository]

💜 DESCRIPTION 💜

Pull the latest changes from a remote repository. literally just grab the fresh stuff from over there 💖

The remote repository may be specified on the command line, but defaults to branch.<name>.remote from the git configuration, or "origin" if not configured. iykyk, git already knows where home is 🏠

Here's the whole vibe of what this command does, step by step, no cap:

  1. pops all currently applied patches from the stack
  2. pulls the changes from the remote repository
  3. updates the stack base to the new remote HEAD
  4. finally pushes all formerly applied patches back onto the stack
⚠️ merge conflicts may occur during that final push step, and those conflicts need to be resolved manually. not me manifesting conflict markers 😭 it happens, just fix them by hand.

See git-fetch(1) for the format of the remote repository argument 📎

✨ OPTIONS ✨

  • -n, --nopush — do not push back patches after pulling. like, we pull and then we just… don't put them back 💀
  • -m, --merged — check for patches that may have been merged upstream. when pushing-back patches, each patch is checked to see if its changes already exist in the just-pulled upstream changes. if a patch's changes have already been merged upstream, the patch will still exist in the stack, but become empty after the pull operation 👑 (iconic, honestly — still there, just hollowed out)
  • --conflicts[=<policy>] — either "allow" or "disallow" pushing a patch with conflicts.
    • using --conflicts=allow (or just --conflicts) allows pushing a patch that may result in unresolved merge conflicts. the patch will be pushed and files with conflicts will be left with conflict markers to be resolved manually; or the operation undone with stg undo --hard. this is the default behavior and also corresponds to the "stgit.push.allow-conflicts" variable being set to "true" 🙈
    • using --conflicts=disallow disallows pushing any patch that would result in merge conflicts. the operation will stop on the last patch that can be pushed without conflicts. this behavior can be configured by setting "stgit.push.allow-conflicts" to "false" 🚫

🌈 STGIT 🌈

part of the StGit suite — see stg(1) ⭐

and that's the whole page, bestie 🍓 this one's from StGit 2.7.0, dated 10/17/2026 — go forth and pull, you absolute main character 💅💖

📦 where this page comes from