git-utils | R Documentation |
prepare_git_repo_for_work()
and git_commit()
are used internally by updateBiocPackageRepoObjects()
to perform Git operations.
prepare_git_repo_for_work(repopath=".", branch=NULL, git=NULL,
use.https=FALSE)
git_commit(repopath=".", commit_msg, push=FALSE,
git=NULL, user_name=NULL, user_email=NULL)
repopath |
The path (as a single string) to the local Git repository of a Bioconductor package. If the specified path exists, If the specified path does not exist, |
branch |
The branch (as a single string) of the Git repository to work on. If |
git |
The path (as a single string) to the git command if it's not in the PATH. |
use.https |
By default, |
commit_msg |
The Git commit message. |
push |
Whether to push the changes or not. Changes are committed but not
pushed by default. You need push access to the package Git repository
at git.bioconductor.org in order to use |
user_name , user_email |
Set the Git user name and/or email to use for the commit. This overrides
the Git user name and/or email that the git command would otherwise use.
See the COMMIT INFORMATION section in
|
prepare_git_repo_for_work()
returns FALSE
if the supplied
path already exists, and TRUE
if it didn't exist and needed
to be cloned.
git_commit()
returns an invisible NULL
.
updateBiocPackageRepoObjects
which uses
prepare_git_repo_for_work
and git_commit
internally.
bump_pkg_version
.
repopath <- file.path(tempdir(), "IdeoViz")
## We must use HTTPS access to clone the package because we are
## not maintainers of the IdeoViz package. A more realistic situation
## would be to use prepare_git_repo_for_work() on a package that we
## maintain, in which case 'use.https=TRUE' would not be needed:
prepare_git_repo_for_work(repopath, use.https=TRUE)
bump_pkg_version(repopath, update.Date=TRUE)
git_commit(repopath, commit_msg="version bump", push=FALSE)
unlink(repopath, recursive=TRUE)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.