Provided by: glab_1.32.0-1ubuntu0.1_amd64 bug

NAME

       glab-release-create - Create a new or update a GitLab Release for a repository

SYNOPSIS

       glab release create  [...] [flags]

DESCRIPTION

       Create a new or update a GitLab Release for a repository.

       If the release already exists, glab updates the release with the new info provided.

       If a Git tag specified does not yet exist, the release will automatically get created from
       the latest state of the default branch and tagged with the specified tag name.  Use  --ref
       to  override  this.   The ref can be a commit SHA, another tag name, or a branch name.  To
       fetch the new tag locally after the release, do git fetch --tags origin.

       To create a release from an annotated Git tag, first create one locally with Git, push the
       tag to GitLab, then run this command.

       Developer level access to the project is required to create a release.

OPTIONS

       -a,  --assets-links=""       JSON  string  representation  of assets links (e.g. --assets-
       links='[{"name": "Asset1", "url":"https://<domain>/some/location/1", "link_type": "other",
       "filepath": "path/to/file"}]')

       -m, --milestone=[]      The title of each milestone the release is associated with

       -n, --name=""      The release name or title

       -N, --notes=""      The release notes/description. You can use Markdown

       -F, --notes-file=""      Read release notes file. Specify - as value to read from stdin

       -r,  --ref=""       If  a tag specified doesn't exist, the release is created from ref and
       tagged with the specified tag name. It can be a commit SHA, another tag name, or a  branch
       name.

       -D,  --released-at=""      The date when the release is/was ready. Defaults to the current
       datetime. Expected in ISO 8601 format (2019-03-15T08:00:00Z)

OPTIONS INHERITED FROM PARENT COMMANDS

       --help[=false]      Show help for command

       -R, --repo=""      Select another repository using the OWNER/REPO or  GROUP/NAMESPACE/REPO
       format or full URL or git URL

EXAMPLE

              Interactively create a release
              $ glab release create v1.0.1

              Non-interactively create a release by specifying a note
              $ glab release create v1.0.1 --notes "bugfix release"

              Use release notes from a file
              $ glab release create v1.0.1 -F changelog.md

              Upload a release asset with a display name (type will default to 'other')
              $ glab release create v1.0.1 '/path/to/asset.zip#My display label'

              Upload a release asset with a display name and type
              $ glab release create v1.0.1 '/path/to/asset.png#My display label#image'

              Upload all assets in a specified folder (types will default to 'other')
              $ glab release create v1.0.1 ./dist/*

              Upload all tarballs in a specified folder (types will default to 'other')
              $ glab release create v1.0.1 ./dist/*.tar.gz

              Create a release with assets specified as JSON object
              $ glab release create v1.0.1 --assets-links='
                [
                  {
                    "name": "Asset1",
                    "url":"https://<domain>/some/location/1",
                    "link_type": "other",
                    "filepath": "path/to/file"
                  }
                ]'

SEE ALSO

       glab-release(1)