Skip to content

Commit 5ba612f

Browse files
aatmmraatmmr
authored
Initial commit
0 parents  commit 5ba612f

File tree

11 files changed

+787
-0
lines changed

11 files changed

+787
-0
lines changed

‎.github/workflows/delete-workflows.yml‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
name: Delete Workflows
2+
3+
on: [workflow_dispatch]
4+
5+
jobs:
6+
do:
7+
runs-on: ubuntu-latest
8+
steps:
9+
- name: Delete workflow runs
10+
uses: Mattraks/[email protected]
11+
with:
12+
retain_days: 0
13+
keep_minimum_runs: 0
14+

‎.github/workflows/init.yml‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
name: Init
2+
3+
on: [create, workflow_dispatch]
4+
5+
permissions:
6+
issues: write
7+
contents: read
8+
9+
jobs:
10+
initialize_repo:
11+
runs-on: ubuntu-latest
12+
if: ${{ github.ref == 'refs/heads/main' }}
13+
steps:
14+
- name: Checkout
15+
uses: actions/[email protected]
16+
- name: Create Issue
17+
env:
18+
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
19+
run: |
20+
gh issue create -t "❓ What is your experience with GitHub?" -b "What is your experience with GitHub? Whats is your experience with other CI/CD tools? Comment below 👇"
21+
gh issue create -t "❓ What do you want to learn?" -b "What is it you want to learn? What specific scenarios are you interrested in? Comment below 👇"
22+
gh issue create -t "🔍 Retro Day one: What was good?" -b "What did you like on day one of this course? What was good? Comment below 👇"
23+
gh issue create -t "🔍 Retro Day one: What can be improved?" -b "What can be improved? What was missing? Any additional comments? Comment below 👇"
24+
gh issue create -t "❤️ What was the best feature you learned yesterday?" -b "What was the GitHub Actions feature you liked best that you have learned about yesterday the first time? If you want add your hobby to share it with the group. Comment below 👇"
25+
gh issue create -t "🔍 Retro Day two: What was good?" -b "What did you like on day two of this course? What was good? Comment below 👇"
26+
gh issue create -t "🔍 Retro Day two: What can be improved?" -b "What can be improved? What was missing? Any additional comments? Comment below 👇"

‎.gitignore‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
.DS_Store

‎CheatSheet.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Cheat Sheet
2+
3+
This document contains an overview of fundamental concepts and terminology, you can use this as a reference book if you get lost in the terminology along the way.
4+
5+
## Github actions high level components
6+
7+
<img width="671" alt="image" src="https://user-images.githubusercontent.com/10853833/216319332-3d5529e8-abfc-4dab-b9b7-e55c4cba99e5.png">
8+
9+
## Yaml functions
10+
11+
| Function | Description |
12+
|---------------------------------|-------------------------------------------------------------------------------------------------------|
13+
| success() | Returns true if none of the previous steps have failed or been cancelled. |
14+
| always() | Returns true even if a previous step was cancelled and causes the step to always get executed anyway. |
15+
| cancelled() | Returns only true if the workflow was canceled. |
16+
| failure() | Returns true if a previous step of the job had failed. |
17+
| contains(search, item) | Returns true if search contains item. |
18+
| startsWith(search, item) | Returns true if search starts with item. |
19+
| endsWith(search, item) | Return true if search ends with item. |
20+
| format('{0} {1}', item1, item2) | Replaces placeholders in a string. |
21+
| join(array, separator) | All values in array are concatenated into a string using provided separator |
22+
| toJSON(value) | Returns a pretty-print JSON representation of value. |
23+
| fromJSON(value) | Returns a JSON object or JSON data type for value. |
24+
25+
## Workflow commands
26+
27+
See also:
28+
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions
29+
Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks.
30+
Most workflow commands use the echo command in a specific format, while others are invoked by writing to a file.
31+
32+
Example echo workflow command:
33+
```bash
34+
echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
35+
```
36+
Example write to file workflow command:
37+
```bash
38+
echo "SELECTED_COLOR=green" >> $GITHUB_OUTPUT
39+
```

‎GettingReady.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Getting ready
2+
3+
## Step 1: Set up your GitHub.com account
4+
5+
For this class, we will use a public account on GitHub.com. We do this for a few reasons:
6+
7+
We don't want you to "practice" in repositories that contain real code.
8+
We are going to break some things, so we can teach you how to fix them (therefore, refer to the line above).
9+
10+
You can set up your free account by following these steps:
11+
12+
* Access [GitHub.com](https://github.com) and click Sign up
13+
* Choose the free account
14+
* You will receive a verification email at the address provided
15+
* Click the link to complete the verification process
16+
* If you already have an account, verify that you can visit github.com within your organization's network.
17+
18+
GitHub is designed to run on the current versions of all major browsers. Take a look at our list of supported browsers.

‎LICENSE‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2022 Michael Kaufmann
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

‎README.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# GitHub Actions Fundamentals
2+
3+
Repo for the `GitHub Actions Fundamentals` training.
4+
5+
## 👉 Objectives
6+
7+
- Understand the __basic components__ and vocabulary of GitHub Actions
8+
- Understand the __YAML__ syntax (scalar types, quotes, literal blocks, maps, and sequences)
9+
- Understand the __workflow syntax__ and how to write workflows using intellisense
10+
- Understand events that can __trigger__ workflows
11+
- Learn the __context and expression syntax__ as well as workflow commands
12+
- Know the different types of __actions__ and how to create/publish them
13+
- Understand the different hosting options for __runners__
14+
- Use __Secrets__ and __Environments__ for staged deployments
15+
- Workflow templates and __reusable workflows__
16+
17+
## Getting ready
18+
19+
Please follow [these instructions](GettingReady.md) and make sure you have set up everything correctly following the [prerequisites](#-prerequisites).
20+
21+
## 📆 Agenda
22+
23+
### Day 1: 🚀 Getting started
24+
25+
- [ ] Introduction and Icebreaker
26+
- [ ] GitHub Actions Fundamentals
27+
- [ ] The YAML syntax
28+
- [ ] Basic workflow syntax
29+
- [ ] Events that trigger workflow
30+
- [ ] Jobs and steps
31+
- [ ] :mag: Demo: Creating a workflow
32+
- [ ] 🔨 Hands-on: [My first Action workflow](hol/01-My-first-workflow.md)
33+
- [ ] Advanced [workflow syntax](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
34+
- [ ] :coffee: Break
35+
- [ ] GitHub Actions
36+
- [ ] Types of Actions
37+
- [ ] 🔨 Hands-on: [My first container Action](hol/02-My-first-action.md)
38+
- [ ] Typescript and composite actions
39+
- [ ] Sharing and releasing actions
40+
- [ ] Using the GitHub API and Octokit
41+
- [ ] Job descriptions
42+
43+
### Day 2
44+
- [ ] Introduction
45+
- [ ] Actions for CI/CD
46+
- [ ] Permissions for GitHub Token
47+
- [ ] Environments and Secrets
48+
- [ ] Staged deployments with environments, approvals, and deployment gates
49+
- [ ] 🔨 Hands-on: [Staged deployments](hol/03-Staged-deployments.md)
50+
- [ ] :coffee: Break
51+
- [ ] Action policies
52+
- [ ] Running your workflows
53+
- [ ] Sharing workflows
54+
- [ ] 🔨 Hands-on: [Reusable workflows](hol/04-Reusable-workflows.md)
55+
- [ ] Best practices and security
56+
57+
58+
## ⚡ Prerequisites
59+
60+
The workshop is designed for developers that have used other platforms like Azure DevOps, GitLab, or Bitbucket and now want to switch to GitHub. But it is also suitable for people that are new to topics like git, CI/CD, and DevOps.
61+
62+
For this workshop you need the following:
63+
64+
- A laptop (Windows, Mac, or Linux)
65+
- A free account for https://github.com
66+
- It is recommended to have a second screen for the hand-on labs
67+
68+
## Cheat Sheet
69+
Find common terminology for reference [here](./CheatSheet.md)
70+

‎hol/01-My-first-workflow.md‎

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
# 🔨 Hands-on: My first workflow
2+
3+
In this hands-on lab your will create your first GitHub Actions Workflow and learn how you can use Actions to automate tasks in your software development lifecycle. If you like more background information, please refer to the [GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions) pages on GitHub Docs. Good luck! 👍
4+
5+
This hands on lab consists of the following steps:
6+
- [Creating a repository](#creating-a-repository)
7+
- [Creating the workflow](#creating-the-workflow)
8+
- [Viewing your workflow results](#viewing-your-workflow-results)
9+
10+
## Creating a repository
11+
12+
Go to [The ActionsFundamentals repository in the ps-actions-sandbox organization](https://github.com/ps-actions-sandbox/ActionsFundamentals) and click <kbd>Use this template</kbd>:
13+
14+
<img width="400" alt="2022-09-18_11-24-58" src="https://user-images.githubusercontent.com/5276337/190895393-6fa0fad9-e05c-4fea-8126-a291b087d663.png">
15+
16+
Select your GitHub user as the owner and name the repository. Leave the repo public to have unlimited action minutes:
17+
18+
<img width="400" alt="2022-09-18_11-25-57" src="https://user-images.githubusercontent.com/5276337/190895398-751a1ec9-c1cf-497f-beb7-a6b53d4d911e.png">
19+
20+
Continue now in the new repository.
21+
22+
## Creating the workflow
23+
24+
Go to **Actions** | [New Workflow](/../../actions/new) and click on [set up a workflow yourself](/../../new/main?filename=.github%2Fworkflows%2Fmain.yml&workflow_template=blank).
25+
26+
1. Rename the file `main.yml` in the `.github/workflows` directory to `github-actions-demo.yml`.
27+
<img width="400" alt="image" src="https://user-images.githubusercontent.com/5276337/174096754-4e2d7219-9caf-42e8-bfd9-c190762886d3.png">
28+
29+
2. Remove the template content - we want to create the workflow from scratch.
30+
3. Click <kbd>Ctrl</kbd>+<kbd>Space</kbd> and select name as the first element:
31+
32+
<img width="400" alt="image" src="https://user-images.githubusercontent.com/5276337/174097468-8be92e37-7948-4895-b5ed-20a22c5773bc.png">
33+
34+
4. Set the workflow name to `GitHub Actions Demo`:
35+
36+
```YAML
37+
name: GitHub Actions Demo
38+
```
39+
40+
5. Add the triggers to the worklow with the help of <kbd>Ctrl</kbd>+<kbd>Space</kbd> and the documentation. We want the workflow to trigger:
41+
- on every push to the `main` branch, but not when there are changes to files in the `.github` folder.
42+
- on every pull request with `main` as the base branch
43+
- Every sunday at 6:15 UTC
44+
- Manually
45+
46+
<details>
47+
<summary>Solution</summary>
48+
49+
```YAML
50+
on:
51+
push:
52+
branches: [ main ]
53+
paths-ignore: [.github/**]
54+
pull_request:
55+
branches: [ main ]
56+
schedule:
57+
- cron: '15 6 * * 0'
58+
workflow_dispatch:
59+
```
60+
61+
</details>
62+
63+
6. Create a job `Build` that runs on the latest Ubuntu image on GitHub hosted runners. Check the documentation of the [virtual environments](https://github.com/actions/virtual-environments/) what label to use and what version it is. The job should do the following things:
64+
- Output the name of the event that triggered the workflow
65+
- Output the name of the branch that the repository is currently referencing
66+
- List all files in the repository
67+
68+
<details>
69+
<summary>Solution</summary>
70+
71+
```YAML
72+
jobs:
73+
Build:
74+
runs-on: ubuntu-latest
75+
steps:
76+
- run: |
77+
echo "🎉 The job was triggered by event: ${{ github.event_name }}"
78+
echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ."
79+
80+
- uses: actions/[email protected]
81+
82+
- name: List files in the repository
83+
run: |
84+
echo "The repository ${{ github.repository }} contains the following files:"
85+
tree
86+
```
87+
88+
</details>
89+
90+
7. Commit the workflow file - and trigger the workflow manually. It should not run automatically if your path filter works. Go to [Action](/../../Actions), select [GitHub Actions Demo](/../../actions/workflows/github-actions-demo.yml) and `Run workflow`:
91+
92+
<img width="600" alt="image" src="https://user-images.githubusercontent.com/5276337/174105162-19f33fd1-8533-4860-9279-88fabec84451.png">
93+
94+
95+
## Viewing your workflow results
96+
97+
1. Click on your workflow run:
98+
99+
<img width="600" alt="image" src="https://user-images.githubusercontent.com/5276337/174105747-0e205e0d-37cc-464c-905b-5b29be74fc75.png">
100+
101+
2. Click on the job 'Build':
102+
103+
<img width="400" alt="image" src="https://user-images.githubusercontent.com/5276337/174105990-a1c204c6-fb7d-44a4-9343-6982899edb25.png">
104+
105+
3. Expand `Set up job` and note the log with the line number (line numbers are links). Check the information about the virtual environment and included software:
106+
107+
<img width="600" alt="image" src="https://user-images.githubusercontent.com/5276337/174106759-c2a8f933-74cf-42a4-899b-b29dc67eccd7.png">
108+
109+
4. Expand your jobs and check that the output was correct.
110+
111+
<img width="400" alt="image" src="https://user-images.githubusercontent.com/5276337/174107136-af9187c1-dbee-4109-9ddc-f2abd4830282.png">
112+
113+
5. Verify your other triggers by modifying the [README.md](/README.md) file:
114+
- Modify and commit: triggers build (`push`)
115+
- Modify and add `[skip ci]` (not triggering the workflow):
116+
<img width="350" alt="image" src="https://user-images.githubusercontent.com/5276337/174110845-93d4a38a-9c8a-4336-9b6a-9089ea9a1cfd.png">
117+
118+
- Modify the [README.md](/README.md) file and create a pull request (trigger: `pull_request`)
119+
120+
## Summary
121+
122+
In this hands-on you've learned to create you first workflow with triggers, jobs, steps, and expressions. Next you will write your [first GitHub Action](02-My-first-action.md).

0 commit comments

Comments
 (0)