gbp-create-remote-repo(1)

✨ gbp-create-remote-repo(1) β€” git-buildpackage Manual πŸ’–

okay bestie, welcome to the glow-up zone πŸŽ€ this is the manual page for gbp-create-remote-repo, one of the little icons living inside the git-buildpackage suite. it makes a git repo somewhere far away (over ssh, so very long-distance relationship energy 🌈) and then yeets your local repo into it. so slay.


πŸ¦‹ NAME

gbp-create-remote-repo β€” Create a remote Git repository ✨


🌸 SYNOPSIS

gbp create-remote-repo [--version] [--help] [--verbose]
                       [--color=[auto|on|off]] [--color-scheme=
                       COLOR_SCHEME] [--remote-url-pattern= url-pattern]
                       [--remote-name= name] [--template-dir= directory]
                       [--remote-config= config] [--[no-]pristine-tar]
                       [--debian-branch= branch_name]
                       [--upstream-branch= branch_name] [--[no-]track]
                       [--[no-]bare] [create | list]

like, that's the whole vibe of the command right there πŸ’…


πŸ’œ DESCRIPTION

gbp create-remote-repo is the friend that goes out and makes you a repository at a remote location via ssh, then pushes your local repository right on into it 🫢. after that it sets up remote branch tracking, so you can just run gbp pull and your repository gets updated from there. no cap.

Before it does literally anything at all on the remote location, it will print the remote URL and ask for confirmation. it's a "hey bestie, is this the right one? πŸ‘€" moment. so good.

Note: By default, the remote repositories are created in the collab-maint repository on git.debian.org. iykyk.

When you invoke it with list, it lists the available remote config templates ✨.


πŸ‘‘ OPTIONS

  • --version β€” print the version of the program, i.e. the version of the git-buildpackage suite 🌟
  • -v, --verbose β€” verbose execution. it says the things. all of them πŸ’¬
  • -h, --help β€” print help and exit πŸ™ˆ
  • --color=[auto|on|off] β€” whether to use colored output 🎨
  • --color-scheme=COLOR_SCHEME β€” the colors to use in output (when color is enabled, okay?). the format for COLOR_SCHEME is '<debug>:<info>:<warning>:<error>'. numerical values and color names are both accepted, and empty fields imply the default color. for example, --git-color-scheme='cyan:34::' would show debug messages in cyan, info messages in blue, and other messages in default (i.e. warning and error messages in red) 🌈
  • --remote-url-pattern=pattern β€” where to create the remote repository. the part %(pkg)s will be replaced by the package name πŸ“
  • --remote-name=name β€” what name git will use when referring to that repository, e.g. 'origin' πŸ’«
  • --template-dir=directory β€” template directory to pass to git init on the remote side. this can be used to customize the remote repository, e.g. to set up hooks πŸͺ
  • --remote-config=config β€” name of a config file section in gbp.conf that specifies the above parameters. see the gbp.conf(5) manpage for details πŸ““
  • --debian-branch=branch_name β€” the branch in the Git repository the Debian package is being developed on, default is master πŸ’…
  • --upstream-branch=branch_name β€” the branch in the Git repository the upstream sources are put onto. default is upstream 🌊
  • --pristine-tar β€” whether to push the pristine-tar branch 🧚
  • --[no-]track β€” whether to set up branch tracking for the debian, upstream and pristine-tar branches πŸ‘€
  • --[no-]bare β€” whether the remote repository should be a bare repository (this is the default) πŸŽ€

πŸ“œ CONFIGURATION FILES

Several gbp.conf files are parsed to set defaults for the above command-line arguments. see the gbp.conf(5) manpage for details πŸ”₯


🌟 SEE ALSO

gbp-buildpackage(1), gbp-pull(1), gbp.conf(5)


🫢 AUTHOR

Guido GΓΌnther <agx@sigxcpu.org> β€” iconic behavior, honestly.


and that's the whole page, bestie πŸ’– this was the gbp-create-remote-repo(1) page from the git-buildpackage Manual, dated 26 May 2026. go forth and create remote repositories, you absolute main character πŸ‘‘βœ¨

πŸ“¦ where this page comes from