1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
.Dd @PACKAGE_DATE@
.Dt GCLI-SNIPPETS 1
.Os @PACKAGE_STRING@
.Sh NAME
.Nm gcli snippets
.Nd manage Gitlab snippets
.Sh SYNOPSIS
.Nm
.Op Fl l
.Op Fl s
.Op Fl n Ar n
.Nm
.Cm delete
.Ar snippet-id
.Nm
.Cm get
.Ar snippet-id
.Sh DESCRIPTION
Use
.Nm
to list, create, download or delete GitLab snippets.
Without a subcommand specified,
.Nm
will list all of your own snippets.
.Sh OPTIONS
.Bl -tag -width indent
.It Fl l , -long
Print a long list instead of a short table.
.It Fl s , -sorted
Reverse the output such that most recent items appear at the bottom.
.It Fl n , -count Ar n
Fetch at least
.Ar n
snippets. Setting
.Ar n
to -1 will fetch all snippets. Default: 30. Note that on users with
many snippets fetching all snippets can take a considerable amount of
time and may result in rate limiting by the GitLab API.
.El
.Sh SUBCOMMANDS
.Bl -tag -width indent
.It Cm delete
Delete a snippet.
.It Cm get
Fetch the raw contents of the snippet.
.El
.Sh EXAMPLES
List all of your snippets:
.Bd -literal -offset indent
$ gcli -t gitlab snippets
.Ed
.Pp
Delete snippet with id 69420:
.Bd -literal -offset indent
$ gcli -t gitlab snippets delete 69420
.Ed
.Pp
Print snippet with id 69420 into your pager:
.Bd -literal -offset indent
$ gcli -t gitlab snippets get 69420 | $PAGER
.Ed
.Sh SEE ALSO
.Xr git 1 ,
.Xr gcli 1
.Sh AUTHORS
.An Nico Sonack aka. herrhotzenplotz Aq Mt nsonack@herrhotzenplotz.de
and contributors.
.Sh BUGS
.Bl -dash
.It
This subcommand only works on Gitlab. It is not implemented for
GitHub, as GitHub Gists work differently.
.It
Creating snippets is currently unimplemented.
.It
There is no
.Fl y
flag to ask the user whether he is sure about deleting a snippet.
.El
.Pp
Please report bugs via E-Mail to
.Mt @PACKAGE_BUGREPORT@ .
.Pp
Alternatively you can report them on any of the forges linked at
.Lk @PACKAGE_URL@ .
However, the preferred and quickest method is to use the mailing
list.
|
