Actions: tidyverse/ggplot2
Actions
Showing runs from all workflows
4,646 workflow runs
4,646 workflow runs
x/y = NULL
turns default axis labels into "x" / "y"
instead of keeping the variable names of the next layer
pr-commands.yaml
#8104:
Issue comment #6616 (comment)
created
by
cararthompson
x/y = NULL
turns default axis labels into "x" / "y"
instead of keeping the variable names of the next layer
pr-commands.yaml
#8103:
Issue comment #6616 (comment)
created
by
teunbrand
GeomSf$default$linetype
work in the same way as linewidth etc?
pr-commands.yaml
#8102:
Issue comment #6543 (comment)
created
by
teunbrand
x/y = NULL
turns default axis labels into "x" / "y"
instead of keeping the variable names of the next layer
pr-commands.yaml
#8101:
Issue comment #6616 (comment)
created
by
cararthompson
x/y = NULL
turns default axis labels into "x" / "y"
instead of keeping the variable names of the next layer
pr-commands.yaml
#8099:
Issue comment #6616 (comment)
created
by
cararthompson
guide_colourbar()
ticks behaviour
R-CMD-check.yaml
#3552:
Pull request #6660
opened
by
teunbrand
guide_colourbar()
ticks behaviour
pkgdown.yaml
#2990:
Pull request #6660
opened
by
teunbrand
guide_colourbar()
ticks behaviour
test-coverage.yaml
#3489:
Pull request #6660
opened
by
teunbrand
x/y = NULL
turns default axis labels into "x" / "y"
instead of keeping the variable names of the next layer
pr-commands.yaml
#8095:
Issue comment #6616 (comment)
created
by
teunbrand
type
options in default colour/fill scales
R-CMD-check.yaml
#3551:
Pull request #6658
opened
by
teunbrand
type
options in default colour/fill scales
test-coverage.yaml
#3488:
Pull request #6658
opened
by
teunbrand
type
options in default colour/fill scales
pkgdown.yaml
#2989:
Pull request #6658
opened
by
teunbrand
x/y = NULL
turns default axis labels into "x" / "y"
instead of keeping the variable names of the next layer
pr-commands.yaml
#8094:
Issue comment #6616 (comment)
created
by
cararthompson
ggplotGrob
inside future::future_lapply
with multisession plan
pr-commands.yaml
#8093:
Issue comment #6464 (comment)
created
by
teunbrand