https://github.com/parmentf/actions-labo
To learn/experiment with GitHub Actions
https://github.com/parmentf/actions-labo
Last synced: 12 months ago
JSON representation
To learn/experiment with GitHub Actions
- Host: GitHub
- URL: https://github.com/parmentf/actions-labo
- Owner: parmentf
- Created: 2023-06-16T07:49:45.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2023-12-08T13:18:59.000Z (over 2 years ago)
- Last Synced: 2024-04-09T01:30:33.824Z (almost 2 years ago)
- Language: Shell
- Size: 864 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# actions-labo
To learn/experiment with GitHub Actions.
## Quickstart
First PR is [#1](https://github.com/parmentf/actions-labo/pull/1), which applies
the [Quickstart](https://docs.github.com/en/actions/quickstart) example.
In fact, although colleagues told me that only workflows in the `main` branch
are taken into account, this seems to be wrong: I added
`.github/workflows/actions-demo.yml` in the `parmentf-patch-1` branch, and it
worked.
I think it depends the `on:` rule (which, in that case, was `push`).
The
[docker-publish](https://github.com/actions/starter-workflows/blob/main/ci/docker-publish.yml)
workflow could be of some help later.
The [actions/create-release](https://github.com/actions/create-release) is interesting too.
## VSCode
Installing [GitHub
Actions](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-github-actions)
extension may help.
## Learn GitHub Actions
Add a workflow in the `main` branch, as stated in Learn GitHub Actions / Understand GitHub Actions / [Create an example workflow](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions).