glab-release-create(1)

1glab(1)                                                                glab(1)
2
3
4

NAME

6       glab-release-create  -  Create  a  new or update a GitLab Release for a
7       repository
8
9
10

SYNOPSIS

12       glab release create  [...] [flags]
13
14
15

DESCRIPTION

17       Create a new or update a GitLab Release for a repository.
18
19
20       If the release already exists, glab updates the release  with  the  new
21       info provided.
22
23
24       If  a  Git tag specified does not yet exist, the release will automati‐
25       cally get created from the latest  state  of  the  default  branch  and
26       tagged  with  the specified tag name.  Use --ref to override this.  The
27       ref can be a commit SHA, another tag name, or a branch name.  To  fetch
28       the new tag locally after the release, do git fetch --tags origin.
29
30
31       To create a release from an annotated Git tag, first create one locally
32       with Git, push the tag to GitLab, then run this command.
33
34
35       Developer level access to the project is required to create a release.
36
37
38

OPTIONS

40       -a, --assets-links=""      JSON string representation of  assets  links
41       (e.g.     --assets-links='[{"name":    "Asset1",    "url":"https://<do‐
42       main>/some/location/1",     "link_type":      "other",      "filepath":
43       "path/to/file"}]')
44
45
46       -m,  --milestone=[]      The title of each milestone the release is as‐
47       sociated with
48
49
50       -n, --name=""      The release name or title
51
52
53       -N, --notes=""      The release notes/description. You can use Markdown
54
55
56       -F, --notes-file=""      Read release notes file. Specify - as value to
57       read from stdin
58
59
60       -r, --ref=""      If a tag specified doesn't exist, the release is cre‐
61       ated from ref and tagged with the specified tag name. It can be a  com‐
62       mit SHA, another tag name, or a branch name.
63
64
65       -D,  --released-at=""       The date when the release is/was ready. De‐
66       faults  to  the  current  datetime.  Expected  in   ISO   8601   format
67       (2019-03-15T08:00:00Z)
68
69
70

OPTIONS INHERITED FROM PARENT COMMANDS

72       --help[=false]      Show help for command
73
74
75       -R,  --repo=""       Select  another repository using the OWNER/REPO or
76       GROUP/NAMESPACE/REPO format or full URL or git URL
77
78
79

EXAMPLE

81       Interactively create a release
82       $ glab release create v1.0.1
83
84       Non-interactively create a release by specifying a note
85       $ glab release create v1.0.1 --notes "bugfix release"
86
87       Use release notes from a file
88       $ glab release create v1.0.1 -F changelog.md
89
90       Upload a release asset with a display name (type will default to 'other')
91       $ glab release create v1.0.1 '/path/to/asset.zip#My display label'
92
93       Upload a release asset with a display name and type
94       $ glab release create v1.0.1 '/path/to/asset.png#My display label#image'
95
96       Upload all assets in a specified folder (types will default to 'other')
97       $ glab release create v1.0.1 ./dist/*
98
99       Upload all tarballs in a specified folder (types will default to 'other')
100       $ glab release create v1.0.1 ./dist/*.tar.gz
101
102       Create a release with assets specified as JSON object
103       $ glab release create v1.0.1 --assets-links='
104         [
105           {
106             "name": "Asset1",
107             "url":"https://<domain>/some/location/1",
108             "link_type": "other",
109             "filepath": "path/to/file"
110           }
111         ]'
112
113
114
115
116

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

OPTIONS INHERITED FROM PARENT COMMANDS

EXAMPLE

SEE ALSO