From f8db09c464e4adc1c543cfa7d5019ea779c0bb91 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lu=C3=ADs=20Duarte?= Date: Wed, 3 Apr 2024 08:48:03 +0100 Subject: [PATCH] add suggestions --- gh-actions-workshop/presentation.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/gh-actions-workshop/presentation.md b/gh-actions-workshop/presentation.md index ddff1c3..db5a530 100644 --- a/gh-actions-workshop/presentation.md +++ b/gh-actions-workshop/presentation.md @@ -136,7 +136,13 @@ jobs: with: node-version: 16.13.x cache: npm +... +``` + +--- +```yaml +... - name: Install run: npm ci @@ -177,7 +183,8 @@ A _workflow_ can be triggered by a plentitude of events: - `push` or `pull_request` are the most common (listens for branch pushes or to PR events); - `create` or `delete` listen for branch creation/deletion events; - `workflow_call`, `workflow_dispatch`, and `workflow_run` can chain together _workflows_ via API or by specifying dependencies; - - the `schedule` can make a _workflow_ work on a recurrent basis using _cron job_ syntax. There's a [huge number of events](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows) that can automate almost everything ranging from issues, comments or even automating GitHub Projects. + - the `schedule` can make a _workflow_ work on a recurrent basis using _cron job_ syntax. + - There's a [huge number of events](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows) that can automate almost everything ranging from issues, comments or even automating GitHub Projects. You can automate almost everything in GitHub, the sky is the limit 🚀 @@ -471,7 +478,7 @@ You should create a new repository that is a template of this repo:
- https://github.com/NIAEFEUP/workshop-ci-24 + https://github.com/NIAEFEUP/workshop-ci-24-template