IT:AD:GitHub:Workflows [Notes]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
# IT:AD:GitHub:Workflows #

<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}
* See:
  * [[IT/AD/Bicep/]]
  * [[IT/AD/SWA/]]


</callout>


<panel title="Summary">

</panel>




Basics:

* Terms: 
  * An *Event* triggers a 
  * *Workflow* comprised of one or more serial or parallel 
  * *Jobs*, each running on individual 
  * *Runners*, each comprised of 
  * *Steps* of *Scripts* or *Actions*.
* Steps within one Job running on a single Runner can share data between themselves. 



##### Steps

* Create a `.github` folder
  * Within, create a `workflows` folder.
    * Within, create a `github-actions-spike.yml` file.
* In the `yml` file:
  * Give it a `name`
  * Give it a trigger (`on`).
  * define `jobs` header under which individual custom named jobs are defined.
  * Define what OS to `runs-on` (`linux-latest`, `windows-latest`, or `self-hosted, windows`)
    * `group` (describe another time)

```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is learning and testing out GitHub Actions 🚀
on: [push]
jobs:
  Spikes-GitHub-Actions:
    runs-on: ubuntu-latest
    environment: build_test_environment
    steps:
      - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
      - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
      - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
      - name: Check out repository code
        uses: actions/checkout@v4
      - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
      - run: echo "🖥️ The workflow is now ready to test your code on the runner."
      - name: Use Bash to List files in the repository
        run: |
          ls ${{ github.workspace }}
      - run: echo "🍏 This job's status is ${{ job.status }}."

```


## Resources ##
* https://blog.devops.dev/a-complete-guide-to-creating-github-actions-pipeline-with-yaml-templates-c57f2dbc2d0c