-
-
Notifications
You must be signed in to change notification settings - Fork 50
/
Copy pathrelease_gh.Rd
42 lines (39 loc) · 1.21 KB
/
release_gh.Rd
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
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/release.R
\name{release_gh}
\alias{release_gh}
\title{Create a new release on GitHub}
\usage{
release_gh(bump = "dev", is_cran = bump != "dev")
}
\arguments{
\item{bump}{The bump increment, either "dev", "patch", "minor" or "major".}
\item{is_cran}{Is this release a CRAN release?}
}
\description{
This must be done \strong{before} a CRAN release.
}
\details{
This function does the following:
\itemize{
\item bump description.
\item update default config in inst/
\item commit
\item git tag
\item run \code{inst/hooks/local/consistent-release-tag.R} hook with --release-mode (passing args to hooks
not possible interactively, hence we run in advance).
\item commit and push with skipping \code{inst/hooks/local/consistent-release-tag.R}.
\item autoupdate own config file
\item bump description with dev
\item commit and push DESCRIPTION and .pre-commit-config.yaml
}
}
\section{CRAN release}{
If \code{is_cran} is \code{TRUE}, the workflow is changed slightly:
\itemize{
\item push to release branch, not main.
\item doesn't run \code{\link[=release_complete]{release_complete()}}. This must be done manually after accepted
on CRAN.
}
}
\keyword{internal}