Creating connections | function-in-function style | Define a custom function with gitlab() and a temporary connection

Set up GitLab connection | Define the project | Create a project called testor.main, owned by the user | Check created branch (depending on GitLab, main branch may still be "master") | Open the URL of the project | Add/modify and commit the README.md | Create a new branch named "for-tests" | Add and commit a CI file (".gitlab-ci.yml") | Use the commit created above and add a follow-up comment | Create a first issue (#1) with a follow-up comment | Delete project

API calls | Writing custom gitlab request functions

Quick Start Example | Central features of 'gitlabr' | Set connection and explore the GitLab instance | parameter style | Using GitLab CI with 'gitlabr'

Parse and split a Rmd / Qmd file, and transform as tibble | Combine a parsed tbl Rmd / Qmd file into a new file

Init a new project with everything in one command

create_r_project(): Create a R project with full content skeleton | Transform project as book with lozen template with create_book_project() | add_kit_project(): Add necessary files for any R project | add_kit_package(): Add files necessary for a package, including | Add files to buildignore : add_build_ignore() | Add files to gitignore : add_git_ignore() | Use a dev history file

Packages | Define the name of the principal branch | Connection to GitLab | Create a new project or use an existing project | Create a new project | Get groups | Create the new project | Use an existing project | Get all information about the project | Clone your project and add the skeleton for your product (package, app, bookdown) | Define local installation and clone | Create the skeleton for your product and initiate the CI/CD | Initiate the CI/CD | Manage git tools (branches, commits, issues, etc.) | Create and manage the forge board and wiki | Visualise the status of your project

Packages | Define the name of the principal branch | Connexion to GitHub | Create a new project or use an existing project | Create a new project | Use an existing project | Manipulate your project and add everything needed | Define local installation and clone | Create R project skeleton | Create weekly | Manage a calendar | Add commit templates | Add issue templates | Add CI log check for Code coverage | Push to server | Start main and create a production branch | Protect branches | No autoclose issue and coverage regex | Create the board | Add missing labels | Create the wiki pages | Add some special issues in the board | Add the first issue for the client | Add the issue that will be shown during the kick-off | Add the todo for the Lead Dev

Initiate the Continuous Integration (CI) / Continuous Deployment (CD) | For a R package or a {golem} app | For a book | How can I find the pkgdown/book associated with my project | Continuous deployment on Posit Connect | CD of a pkgdown | Create the pkgdown | Initiate the deployment of your pkgdown | To be done on your R project | To be done on Gitlab | How can I find the pkgdown associated with my R package on Posit Connect | CD of a golem shiny app | Add an app.R at the root of your package to deploy on RStudio Connect | Initiate the deployment of your app | How can I find the app associated with my {golem} package | CD of a book | Build your book | Initiate the deployment of your book | How can I find the book deployed on Posit Connect ?

For a project on Gitlab | Create a weekly for GitLab with gl_create_weekly() | Visualise the nature of the developments for GitLab with visualise_commits() | Visualise the progress of the milestones for GitLab with gl_get_milestones_progress() | For a project on Github

build_pkgdown_with_reports() : build a pkgdown with coverage and test reports

Add labels | Create the board | Add some special issues in the board | Add the first issue for the client | Add the issue that will be shown during the kick-off | Add the todo for the Lead Dev | Create the wiki pages | No autoclose issue and coverage regex | Add commit templates | Add issues templates

Define local installation and clone | Push to server | Create a production branch | Protect branches | No autoclose issue and coverage regex | Add commit templates | Add issues templates

Create book repository inside a package | Create empty book | Build the book based on vignettes | Create short book with index and references only | Help user find the userguides

Create the pkgdown | Help user find the site

Build a reference page | Add references to this page

To describe your package and how to install it | Create and update a custom README with installation instructions

Create a reproducible example of a versioned directory | Build book of commits messages | Read list of commits and extract information | Get commits and find pattern | Create a vignette that lists all files with date of modification

File explorer

parsermd | Installation | Parsing Rmds | Working with the AST | Wildcards | ast as a tibble

Example - hw01 | Constructing a template | Using a template | Revising a template

Create directories to mount in the Docker | Create the table of correspondance for additional volumes | Launch Docker with other volumes

Create new package | Use {renv} inside Docker and keep installation of packages | {renv} and its different storage directories | Activate cache shared on host | Keep "renv_instructions.Rmd" up-to-date

Connexion with a mysql container | Launch Docker | Connect to database inside the container | Stop your db container | Stop RStudio Docker container and the network

Create new package | Launch Docker

Create buffer areas with attribute of the closest region

Extract part of the data with gplot_data | Plot with ggplot2 | Sun position

General use | Installation | Custom parameters | Title page information | Normal page header and footer | Other options | Background | Create your own template | Extra