git-branchless-submit(1)

💖 NAME 💖

okay so this is the git-branchless-submit(1) page from the General Commands Manual, and it’s serving submit — the command whose whole job is: Push commits to a remote ✨ no cap.

🎀 SYNOPSIS 🎀

submit [--hidden] [-F|--forge] [-c|--create] [-d|--draft] [-m|--message]
[-j|--jobs] [-s|--strategy] [-n|--dry-run] [-h|--help] [REVSETS]

🦋 DESCRIPTION 🦋

Push commits to a remote. That’s the function, bestie — your commits get sent to the remote, and that’s the whole vibe. 💅

🌸 OPTIONS 🌸

• --hidden — include hidden commits in the results of evaluating revset expressions. Sneaky little commits get to show up too 👀
• -F, --forge <FORGE_KIND> — the Git hosting provider to use, called a “forge”. If you don’t provide one, it’ll try to automatically detect the forge used by the repository. If no forge can be detected, it falls back to the branch forge 🫶

Possible values:

• branch — force-push branches to the default push remote. You can configure the default push remote with git config remote.pushDefault <remote> 💖
• github — force-push branches to the remote and create a pull request for each branch using the gh command-line tool. WARNING: likely buggy! 💀
• phabricator — submit code reviews to Phabricator using the arc command-line tool ✨

• -c, --create — if there is no associated remote commit or code review object for a given local commit, create the remote object by pushing the local commit to the forge. It’s giving “make it exist” energy 🔥
• -d, --draft — if the forge supports it, create code reviews in “draft” mode 🎀
• -m, --message <MESSAGE> — if the forge supports it, an optional message to include with the create or update operation. Say it with your chest, bestie 💌
• -j, --jobs <NUM_JOBS> — if the forge supports it, how many jobs to execute in parallel. The value 0 indicates to use all CPUs ⚡
• -s, --strategy <EXECUTION_STRATEGY> — if the forge supports it and uses a tool that needs access to the working copy, what kind of execution strategy to use 🧚

Possible values:

• working-copy — Default. Run the tests in the working copy. This requires a clean working copy. This is useful if you want to reuse build artifacts in the current directory 🌈
• worktree — run the tests in a separate worktree (managed by git-branchless). This is useful if you want to run tests in parallel, or if you want to run tests on a different commit without invalidating build artifacts in the current directory, or if you want to run tests while your working copy is dirty 🌸

• -n, --dry-run — don’t push or create anything. Instead, report what would be pushed or created. (This may still trigger fetching information from the forge.) A little peek behind the curtain, no commitment 👑
• -h, --help — print help (see a summary with -h) 🫶
• [REVSETS] [default: stack()] — the commits to push to the forge. Unless --create is passed, this will only push commits that already have associated remote objects on the forge. iykyk 😌

---

and that’s the tea: submit in git-branchless-submit(1), General Commands Manual edition — the footer gives us no date, just this cute little sign-off, so mwah 💋✨