glab(1)

πŸŽ€ glab(1) β€” glab-issue-create πŸŽ€

✨ NAME ✨

glab-issue-create β€” create an issue. πŸ’– Bestie, this is the command that lets you drop a fresh issue into your GitLab repo, and it's giving main character energy.

πŸ¦‹ SYNOPSIS πŸ¦‹

glab issue create [flags]

🌸 DESCRIPTION 🌸

okay so glab issue create opens an editor so you can draft the issue, unless you pass a title and description. Use --web to create the issue in your browser instead, or --template to start from an issue template. Slay.

--attach uploads a file and references it at the end of the description. Repeat the flag for more than one file, or pass - to read the file from standard input. An attachment satisfies the description requirement, so --title with --attach completes without prompting. lowkey iconic.

⚠️ The --attach flag is an experiment. It might be unstable or removed at any time, and is not ready for production use. For more information, see https://docs.gitlab.com/policy/development_stages_support/.
⚠️ The --recover flag is an experiment: it might be unstable or removed at any time, and is not ready for production use. For more information, see https://docs.gitlab.com/policy/development_stages_support/.

πŸ’… OPTIONS πŸ’…

  • -a, --assignee=[] β€” assign the issue to people by their usernames. Multiple usernames can be comma-separated or specified by repeating the flag. πŸ’–
  • --attach=[] β€” (EXPERIMENTAL) upload a file and reference it at the end of the description. Use "-" to read the file from standard input. Repeat the flag to attach multiple files. πŸŽ€
  • -c, --confidential[=false] β€” set an issue to be confidential. 🀫
  • -d, --description="" β€” issue description. Set to "-" to open an editor. ✍️
  • --description-file="" β€” read the issue description from a file. Use "-" to read from standard input. πŸ“„
  • --due-date="" β€” a date in 'YYYY-MM-DD' format. πŸ“…
  • --epic=0 β€” ID of the epic to add the issue to. πŸ‘‘
  • -l, --label=[] β€” add label by name. Multiple labels can be comma-separated or specified by repeating the flag. 🏷️
  • --link-type="relates_to" β€” type for the issue link. πŸ”—
  • --linked-issues=[] β€” the IIDs of issues that this issue links to. Multiple IIDs can be comma-separated or specified by repeating the flag. πŸ¦‹
  • --linked-mr=0 β€” the IID of a merge request in which to resolve all issues. 🫢
  • -m, --milestone="" β€” the global ID or title of a milestone to assign. ⭐
  • --no-editor[=false] β€” don't open editor to enter a description. If set to true, uses prompt. πŸ™ˆ
  • --recover[=false] β€” save the options to a file if the issue fails to be created. If the file exists, the options will be loaded from the recovery file. (EXPERIMENTAL) πŸ’€
  • --template="" β€” template to pre-populate the description. A name is looked up in '.gitlab/issue_templates/' of the local repository, and the '.md' extension is optional. A value that is absolute or contains a path separator is read as a file path, for example '~/templates/bug.md'. 🧚
  • -e, --time-estimate="" β€” set time estimate for the issue. ⏳
  • -s, --time-spent="" β€” set time spent for the issue. βŒ›
  • -t, --title="" β€” issue title. ✨
  • --web[=false] β€” continue issue creation with web interface. 🌈
  • -w, --weight=0 β€” issue weight. Valid values are greater than or equal to 0. βš–οΈ
  • -y, --yes[=false] β€” don't prompt for confirmation to submit the issue. βœ…

🌟 OPTIONS INHERITED FROM PARENT COMMANDS 🌟

  • -h, --help[=false] β€” show help for this command. 🫢
  • -R, --repo="" β€” select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. πŸ”₯

πŸ“ EXAMPLE πŸ“

glab issue create
glab issue new
glab issue create -m release-2.0.0 -t "we need this feature" --label important
glab issue new -t "Fix CVE-YYYY-XXXX" -l security --linked-mr 123
glab issue create -m release-1.0.1 -t "security fix" --label security --web --recover
glab issue create -t "Bug Report" --template bug
glab issue create -t "Feature Request" --template feature_proposal.md --yes

# Use a template file from outside the repository
glab issue create -t "Bug Report" --template ~/team-templates/bug.md

# Read the description from a file
glab issue create -t "we need this feature" --description-file description.md

# Read the description from standard input
cat description.md | glab issue create -t "we need this feature" --description-file -

# Attach a screenshot to the description
glab issue create -t "Login button misaligned" -d "See below." --attach ./screenshot.png

πŸ‘‘ SEE ALSO πŸ‘‘


okay that's the whole page, bestie! this was auto generated by spf13/cobra, dated Nov 2026, and it's the glab(1) manual β€” byeee πŸ’…πŸ«Ά

πŸ“¦ where this page comes from