REPO(1)

πŸ“¦
version 2.36.1 Β· 3 versions
, in debian bookworm, ubuntu noble

πŸ’– NAME πŸ’–

okay so bestie, welcome to the repo manual page β€” specifically the one for repo gitc-init. that's it, that's the name, periodt. πŸ’…


✨ SYNOPSIS ✨

repo gitc-init [options] [client name]

πŸŽ€ DESCRIPTION πŸŽ€

Summary β€” hold onto your scrunchie:

Initialize a GITC Client. πŸ¦‹


πŸ’… OPTIONS πŸ’…

  • -h, --help β€” pops up this help message and then dips. show's over, bye! πŸ‘‹

🌸 Logging options 🌸

  • -v, --verbose β€” show all the output. every last crumb, no gatekeeping. πŸ“
  • -q, --quiet β€” only show errors. silent treatment mode, but like, productive. πŸ’€

🌈 Manifest options 🌈

  • -u URL, --manifest-url=URL β€” where the manifest repository lives. its address, its home. 🏠
  • -b REVISION, --manifest-branch=REVISION β€” the manifest branch or revision (use HEAD for the default, bestie, just say HEAD). 🌿
  • -m NAME.xml, --manifest-name=NAME.xml β€” the initial manifest file. yes the .xml is part of it, don't @ me. πŸ“„
  • -g GROUP, --groups=GROUP β€” restrict manifest projects to the ones with the specified group(s), and the vibes are [default|all|G1,G2,G3|G4,-G5,-G6]. yes you can negate them, yes it's iconic. ✨
  • -p PLATFORM, --platform=PLATFORM β€” restrict manifest projects to ones with a specified platform group [auto|all|none|linux|darwin|...]. platform-specific slay. πŸ–₯️
  • --submodules β€” sync any submodules hanging around the manifest repo. bring the whole friend group. 🫢
  • --standalone-manifest β€” download the manifest as a static file rather than creating a git checkout of the manifest repo. no clone, just vibes. 🧚
  • --manifest-depth=DEPTH β€” create a shallow clone of the manifest repo with the given depth (0 for a full clone); see git clone (default: 0). lowkey shallow, highkey valid. 🌊

πŸ’œ Manifest (only) checkout options πŸ’œ

  • --current-branch β€” fetch only the current manifest branch from the server (this is the default, btw). one branch, one bestie. ⭐
  • --no-current-branch β€” fetch all the manifest branches from the server. collect them all. πŸŽ€
  • --tags β€” fetch tags in the manifest. tag, you're it. 🏷️
  • --no-tags β€” don't fetch tags in the manifest. nope, no tags today. πŸ™ˆ

πŸ¦‹ Checkout modes πŸ¦‹

  • --mirror β€” create a replica of the remote repositories rather than a client working directory. it's giving mirrorball. πŸͺ©
  • --archive β€” checkout an archive instead of a git repository for each project. see git archive. πŸ“¦
  • --worktree β€” use git-worktree to manage projects. worktree, worktree, worktree. 🌳

πŸ”₯ Project checkout optimizations πŸ”₯

  • --reference=DIR β€” location of the mirror directory. point me to it. πŸ“
  • --dissociate β€” dissociate from the reference mirrors after clone. it's not you, it's the borrow. πŸ’”
  • --depth=DEPTH β€” create a shallow clone with the given depth; see git clone. 🏊
  • --partial-clone β€” perform partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code). half the data, all the energy. ✨
  • --no-partial-clone β€” disable use of partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code). full send, no halves. πŸ’―
  • --partial-clone-exclude=PARTIAL_CLONE_EXCLUDE β€” exclude the specified projects (a comma-delimited list of project names) from partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code). not invited to the partial party. 🚫
  • --clone-filter=CLONE_FILTER β€” the filter for use with --partial-clone [default: blob:none]. the default filter ate and left no crumbs. πŸ‘‘
  • --use-superproject β€” use the manifest superproject to sync projects; implies -c. superproject has main character energy fr fr. 🦸
  • --no-use-superproject β€” disable use of manifest superprojects. superproject, you're on mute. πŸ”‡
  • --clone-bundle β€” enable use of /clone.bundle on HTTP/HTTPS (default if not --partial-clone). 🎁
  • --no-clone-bundle β€” disable use of /clone.bundle on HTTP/HTTPS (default if --partial-clone). no bundle, we're good. πŸ™…
  • --git-lfs β€” enable Git LFS support. big files deserve love too. 🐘
  • --no-git-lfs β€” disable Git LFS support. not today, LFS. πŸ’€

🧚 repo Version options 🧚

  • --repo-url=URL β€” repo repository location ($REPO_URL). yes it's an env var, yes it's fancy. πŸ’…
  • --repo-rev=REV β€” repo branch or revision ($REPO_REV). pick your era. ⏳
  • --no-repo-verify β€” do not verify repo source code. living dangerously, I see. 😭

🌸 Other options 🌸

  • --config-name β€” Always prompt for name/e-mail. it wants to know who you are. πŸ‘€

πŸ’– GITC options πŸ’–

  • -f MANIFEST_FILE, --manifest-file=MANIFEST_FILE β€” Optional manifest file to use for this GITC client. ✨
  • -c GITC_CLIENT, --gitc-client=GITC_CLIENT β€” Name of the gitc_client instance to create or modify. this one is important, we'll get to it. πŸ”₯

🌈 Multi-manifest 🌈

  • --outer-manifest β€” operate starting at the outermost manifest. go big, start outside. 🌍
  • --no-outer-manifest β€” do not operate on outer manifests. stay in your lane. πŸ›£οΈ
  • --this-manifest-only β€” only operate on this (sub)manifest. just this one, nothing else. 🎯
  • --no-this-manifest-only, --all-manifests β€” operate on this manifest and its submanifests. the whole family tree. 🌳

Run repo help gitc-init to view the detailed manual. like, the actually detailed one. πŸ“–


πŸ‘‘ DETAILS πŸ‘‘

The repo gitc-init command is ran to initialize a new GITC client for use with the GITC file system. that's the whole point of it, bestie. 🫢

This command will setup the client directory, initialize repo, just like repo init does, and then downloads the manifest collection and installs it in the .repo/directory of the GITC client. it's doing the most, and honestly? it's serving. ✨

Once this is done, a GITC manifest is generated by pulling the HEAD SHA for each project and generates the properly formatted XML file and installs it as .manifest in the GITC client directory. cute little XML, freshly baked. πŸ“

The -c argument is required to specify the GITC client name. no -c, no client, no cap. 🚨

The optional -f argument can be used to specify the manifest file to use for this GITC client. optional, unlike -c. πŸ™ˆ


and that's the whole page, bestie β€” repo gitc-init, from the Repo Manual, dated October 2022. go forth and initialize, you absolute icon. πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from