Remember to provide FIREBASE_TOKEN
as a secret to the GitHub UI.
Thin wrapper around GitHub actions.
Configuration details other than PROJECT_ID
are read from the firebase.json
at the root of your repository.
firebase(IDENTIFIER, needs, args, PROJECT_ID = NULL) firebase_deploy(IDENTIFIER = "Deploy", needs, PROJECT_ID = NULL)
IDENTIFIER |
Used:
|
---|---|
needs |
|
args |
|
PROJECT_ID |
|
... | arguments passed on to other methods, not currently used. |
These functions are for advanced users knowledgeable about GitHub actions. Novice users may be better served by the complete templates in workflows.
These functions provide very thin wrappers around existing GitHub actions, including actions from other repositories.
Essentially, they just create lists ready to be ingested by make_action_block()
, which then turns these R lists into valid GitHub actions syntax blocks.
For documentation on these actions, consult their respective README.md
s linked in the below.
Some variants of these action wrappers include sensible defaults for frequent uses in R.
The uses
field is always hardcoded to a particular commit or tag of the underlying github action to ensure compatibility.
To render an action block completely from scratch, you can always use the templating function make_action_block()
.
Because firebase gets the deploy directory from a firebase.json
file, it cannot automatically find the appropriate path.
Manually edit your firebase.json
to provide the deploy path.
firebase_deploy
: Deploy static assets to Firebase Hosting
Other actions: docker_cli
,
document
, filter
,
ghpages
, install_deps
,
netlify
, rscript_byod
,
rsync