GIT-BUG(1)

hey bestie!! welcome to the GIT-BUG(1) manual page — this one is all about git-bug-bridge-new, and it's literally the "configure a new bridge" page. no cap. 💅

💖 NAME 💖

git-bug-bridge-new — configure a new bridge. that's the name section, and honestly it's giving main character setup energy. ✨

✨ SYNOPSIS ✨

the vibe check, command edition:

git-bug bridge new [flags]

🎀 DESCRIPTION 🎀

okay so here's the deal: you configure a new bridge by passing flags or/and using interactive terminal prompts. and if you pass all the necessary flags to configure your bridge, you can avoid all the terminal prompts — like, fully skip them. periodt. 💖

💅 OPTIONS 💅

here is every single flag, bestie — no skips, no cap:

• -n, --name="" — a distinctive name to identify the bridge. 💖
• -t, --target="" — the target of the bridge. valid values are [github,gitlab,jira,launchpad-preview].
• -u, --url="" — the URL of the remote repository.
• -b, --base-url="" — the base URL of your remote issue tracker.
• -l, --login="" — the login on your remote issue tracker.
• -c, --credential="" — the identifier or prefix of an already known credential for your remote issue tracker (see "git-bug bridge auth").
• --token="" — a raw authentication token for the remote issue tracker.
• --token-stdin[=false] — will read the token from stdin and ignore --token.
• -o, --owner="" — the owner of the remote repository.
• -p, --project="" — the name of the remote repository.
• --non-interactive[=false] — do not ask for user input.
• -h, --help[=false] — help for new.

🌈 EXAMPLE 🌈

okay this next part is the full example block, copied exactly, bestie — interactive first, then GitHub, Launchpad, and Gitlab. iykyk. 🦋

# Interactive example
[1]: github
[2]: gitlab
[3]: jira
[4]: launchpad-preview

target: 1
name [default]: default

Detected projects:
[1]: github.com/git-bug/git-bug

[0]: Another project

Select option: 1

[1]: user provided token
[2]: interactive token creation
Select option: 1

You can generate a new token by visiting https://github.com/settings/tokens.
Choose 'Generate new token' and set the necessary access scope for your repository.

The access scope depend on the type of repository.
Public:
     - 'public_repo': to be able to read public repositories
Private:
     - 'repo'       : to be able to read private repositories

Enter token: 87cf5c03b64029f18ea5f9ca5679daa08ccbd700
Successfully configured bridge: default

# For GitHub
git bug bridge new \
    --name=default \
    --target=github \
    --owner=example-owner
    --project=example-repo \
    --token=$TOKEN

# For Launchpad
git bug bridge new \
    --name=default \
    --target=launchpad-preview \
    --url=https://bugs.launchpad.net/ubuntu/

# For Gitlab
git bug bridge new \
    --name=default \
    --target=gitlab \
    --url=https://github.com/example-org/example-repo \
    --token=$TOKEN

🦋 SEE ALSO 🦋

• git-bug-bridge(1) — go peek at the bridge manual too, bestie. 🫶

okay that's the whole page! this manual came from git-bug's source, and the footer has Apr 2019 plus the GIT-BUG(1) name — mwah, bye bestie! 💋✨