git-release(1)

1GIT-RELEASE(1)                    Git Extras                    GIT-RELEASE(1)
2
3
4

NAME

6       git-release - Commit, tag and push changes to the repository
7

SYNOPSIS

9       git-release  [<tagname>  |  --semver  <name>] [-r <remote>] [-m <commit
10       info>] [--no-empty-commit] [-c] [[--] <hook arguments...>]
11

DESCRIPTION

13       Commits changes with  message  "Release  <tagname>"  or  custom  commit
14       information,  tags  with  the  given  <tagname> and pushes the branch /
15       tags.
16
17       This command always creates a release commit, which could be  empty  if
18       nothing changed. It works like git merge --no-ff. If you don´t like the
19       behavior, you could add --no-empty-commit to skip it.
20
21       Optionally it generates a changelog (see git-changelog)  and  a  remote
22       can be defined. The order of first -c or -r does not matter.
23
24       If  .git/hook/pre-release or .git/hook/post-release exist, they will be
25       triggered with  tagname  and  extra  hook  arguments  before/after  the
26       release.
27

OPTIONS

29       --semver <name>
30
31       If  the  latest tag in your repo matches the semver format requirement,
32       you could increase part of it as the new release tag with this  option.
33       The  name  must be one of the major, minor, patch. For example, assumed
34       the latest tag is 4.4.0, with git release --semver minor you will  make
35       a new release with tag 4.5.0.
36
37       <tagname>
38
39       The name of the newly created tag. Also used in tag comment.
40
41       -r <remote>
42
43       The  "remote" repository that is destination of a push operation: it is
44       passed to git push.
45
46       -m <commit info>
47
48       use the custom  commit  information  instead  of  the  default  message
49       "Release <tagname>" .
50
51       --no-empty-commit
52
53       Avoid creating empty commit if nothing could be committed.
54
55       -c
56
57       Generates  or populates the changelog with all commit message since the
58       last tag. For more info see git-changelog..
59
60       [--] hook arguments...
61
62       The  arguments  listed  after  "--"  separator  will   be   passed   to
63       pre/post-release hook following the tagname.
64

EXAMPLES

66       ·   Release commit with the given <tagname>.
67
68           $ git release 0.1.0
69
70       ·   Release commit with the given <tagname> and custom commit message.
71
72           $ git release 0.1.0 -m "+ powerful feature added."
73
74       ·   Release  commit  with  the  given  <tagname>  and  push to specific
75           remote.
76
77           $ git release 0.1.0 -r github
78
79       ·   Release commit with the given <tagname> and populate changelog.
80
81           $ git release 0.1.0 -c
82
83       ·   Release commit with the given <tagname>,  populate  changelog,  and
84           push to specific remote.
85
86           $ git release 0.1.0 -r github -c
87
88       ·   Release  commit  with the given <tagname>, pass <tagname> and extra
89           argument to release hook, populate changelog, and push to  specific
90           remote.
91
92           $ git release 0.1.0 -r github -c -- --signature-required
93
94
95

AUTHOR

97       Written  by Tj Holowaychuk <tj@vision-media.ca> Extended by David Hart‐
98       mann <dh@tsl.io>
99

REPORTING BUGS

101       <https://github.com/tj/git-extras/issues>
102