Updating GHES workflows

Merge pull request #2366 from actions/pages-ghes-3.13
Revert Pages actions to last ones compatible with GHES
2024-04-18 19:39:37 +00:00 · 2024-04-17 17:47:01 -05:00 · 2024-04-11 11:17:41 +00:00 · 2024-04-05 14:22:52 -07:00 · 2024-04-03 15:22:51 +00:00 · 2024-03-30 01:21:25 +00:00
194 changed files with 1413 additions and 2535 deletions
@@ -1,30 +0,0 @@
---
-name: Code Scanning onboarding
-about: Captures all the information and tasks required to onboard a 3rd party project into Code Scanning
-title: 'Code Scanning Partner: '
-labels: 'code scanning'
-assignees: ''
-
---
-
-:wave: Thanks for your interest in integrating with Code Scanning! To ensure a swift onboarding of your integration, please provide the following `Requested information` and complete the `Action items` below:
-
-## Requested information
- [ ] Name of your integration:
- [ ] Name of your product / company:
- [ ] Description of your integration:
- [ ] Languages supported by your integration:
- [ ] [For integrations leveraging GitHub Actions] PR for your proposed workflow:
- [ ] URL to an SVG logo representing your integration / product / company:
-
-## Action items
- [ ] Apply to join the GitHub Technology Partner Program: [partner.github.com/apply](https://partner.github.com/apply?partnershipType=Technology+Partner)
- [ ] Develop your integration, by _either_ [following this guide for GitHub Actions](https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions), or [integrating directly with the REST API](https://docs.github.com/en/rest/reference/code-scanning#upload-a-sarif-file)
- [ ] [For integrations leveraging GitHub Actions] Submit a PR in this repo for your proposed starter workflow. The workflow should:
-	- [ ] Live in [the `code-scanning` directory](https://github.com/actions/starter-workflows/tree/main/code-scanning)
-	- [ ] Have a filename that is in accordance with your product / service / business name, in [_kebab-cased_ format](https://en.wikipedia.org/wiki/Kebab_case), with a `.yml` file extension
-	- [ ] Include comments describing the workflow’s behavior ([example](https://github.com/actions/starter-workflows/blob/c59b62dee0eae1f9f368b7011cf05c2fc42cf084/code-scanning/codeql.yml#L1-L11))
-	- [ ] Trigger on push, pull_request, and schedule events ([example](https://github.com/actions/starter-workflows/blob/c59b62dee0eae1f9f368b7011cf05c2fc42cf084/code-scanning/codeql.yml#L14-L21))
-	- [ ] Reference your GitHub Action using a 40-char commit SHA (e.g. `uses: github/codeql-action@a3a8231e64d3db0e7da0f3b56b9521dcccdfe412`)
- [ ] Update the `Requested information` above, ensuring all details are correct
- [ ] When ready, please ping `@actions/advanced-security-code-scanning` in a comment below, for a review :bow:
@@ -1,14 +1,7 @@
-This repository contains configuration for what users see when they click on the `Actions` tab and the setup page for Code Scanning.
+Thank you for sending in this pull request. Please make sure you take a look at the [contributing file](https://github.com/actions/starter-workflows/blob/master/CONTRIBUTING.md). Here's a few things for you to consider in this pull request:

-It is not:
-* A playground to try out scripts
-* A place for you to create a workflow for your repository
-
---
-
-**Please note that at this time we are only accepting new starter workflows for Code Scanning. Updates to existing starter workflows are fine.**
-
---
+- [ ] Include a good description of the workflow.
+- [ ] Links to the language or tool will be nice (unless its really obvious)

 In the workflow and properties files:

@@ -19,19 +12,20 @@ In the workflow and properties files:
 - [ ] Use sentence case for the names of workflows and steps, for example "Run tests".
 - [ ] The name of CI workflows should only be the name of the language or platform: for example "Go" (not "Go CI" or "Go Build")
 - [ ] Include comments in the workflow for any parts that are not obvious or could use clarification.
- [ ] CI workflows should run on `push` to `branches: [ $default-branch ]` and `pull_request` to `branches: [ $default-branch ]`.
- [ ] Packaging workflows should run on `release` with `types: [ created ]`.
- [ ] Code Scanning workflows should run on `push` to `branches: [ $default-branch, $protected-branches ]` and `pull_request` to `branches: [ $default-branch ]`. We also recommend a `schedule` trigger of `cron: $cron-weekly`.
+- [ ] CI workflows should run on `push` to `branches: [ master ]` and `pull_request` to `branches: [ master ]`.
+
+  Packaging workflows should run on `release` with `types: [ created ]`.

 Some general notes:

 - [ ] This workflow must only use actions that are produced by GitHub, [in the `actions` organization](https://github.com/actions), **or**
- [ ] This workflow must only use actions that are produced by the language or ecosystem that the workflow supports.  These actions must be [published to the GitHub Marketplace](https://github.com/marketplace?type=actions).  We recommend that these actions be referenced using the full 40 character hash of the action's commit instead of a tag.  Additionally, workflows must include the following comment at the top of the workflow file:
+
+  This workflow must only use actions that are produced by the language or ecosystem that the workflow supports.  These actions must be [published to the GitHub Marketplace](https://github.com/marketplace?type=actions).  Workflows using these actions must reference the action using the full 40 character hash of the action's commit instead of a tag.  Additionally, workflows must include the following comment at the top of the workflow file:
    ```
    # This workflow uses actions that are not certified by GitHub.
    # They are provided by a third-party and are governed by
    # separate terms of service, privacy policy, and support
    # documentation.
    ```
- [ ] Automation and CI workflows should not send data to any 3rd party service except for the purposes of installing dependencies.
- [ ] Automation and CI workflows cannot be dependent on a paid service or product.
+- [ ] This workflow must not send data to any 3rd party service except for the purposes of installing dependencies.
+- [ ] This workflow must not use a paid service or product.
@@ -1,19 +0,0 @@
-name: Close as a feature
-on:
-  issues:
-    types: [labeled]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-    - name: Close Issue
-      uses: peter-evans/close-issue@v1
-      if: contains(github.event.issue.labels.*.name, 'feature')
-      with:
-        comment: |
-          Thank you 🙇 for this request. This request has been classified as a feature by the maintainers.
-          
-          We take all the requests for features seriously and have passed this on to the internal teams for their consideration.
-          
-          Because any feature requires further maintenance and support in the long term by this team, we would like to exercise caution into adding new features. If this feature is something that can be implemented independently, please consider forking this repository and adding the feature.
@@ -1,19 +0,0 @@
-name: Close as a support issue
-on:
-  issues:
-    types: [labeled]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-    - name: Close Issue
-      uses: peter-evans/close-issue@v1
-      if: contains(github.event.issue.labels.*.name, 'support')
-      with:
-        comment: |
-          Sorry, but we'd like to keep issues related to code in this repository. Thank you 🙇 
-          
-          If you have questions about writing workflows or action files, then please [visit the GitHub Community Forum's Actions Board](https://github.community/t5/GitHub-Actions/bd-p/actions)
-          
-          If you are having an issue or question about GitHub Actions then please [contact customer support](https://help.github.com/en/articles/about-github-actions#contacting-support)
@@ -1,20 +0,0 @@
-name: Mark stale issues and pull requests
-
-on:
-  schedule:
-  - cron: "21 4 * * *"
-
-jobs:
-  stale:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/stale@v3
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        stale-issue-message: 'This issue has become stale and will be closed automatically within a period of time. Sorry about that.'
-        stale-pr-message: 'This pull request has become stale and will be closed automatically within a period of time. Sorry about that.'
-        stale-issue-label: 'no-issue-activity'
-        stale-pr-label: 'no-pr-activity'
-        days-before-stale: 90 
@@ -1,9 +1,7 @@
-name: Sync workflows for GHES
-
 on:
  push:
    branches:
-    - main
+    - master

 jobs:
  sync:
@@ -24,9 +22,5 @@ jobs:
      working-directory: ./script/sync-ghes
    - run: |
        git add -A
-        if [ -z "$(git status --porcelain)" ]; then
-          echo "No changes to commit"
-        else
-          git commit -m "Updating GHES workflows"
-        fi
-    - run: git push
+        git commit -m "Updating GHES workflows"
+    - run: git push
@@ -1,21 +0,0 @@
-name: Validate Data
-
-on:
-  push:
-  pull_request:
-
-jobs:
-  validate-data:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-
-      - uses: actions/setup-node@v1
-        with:
-          node-version: "12"
-
-      - name: Validate workflows
-        run: |
-          npm ci
-          npx ts-node-script ./index.ts
-        working-directory: ./script/validate-data
@@ -1,3 +0,0 @@
-* @actions/actions-experience
-
-/code-scanning/ @actions/advanced-security-code-scanning
@@ -4,21 +4,17 @@

 Hi there 👋 We are excited that you want to contribute a new workflow to this repo. By doing this you are helping people get up and running with GitHub Actions and that's cool 😎.

-Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](https://github.com/actions/starter-workflows/blob/main/LICENSE).
+Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](https://github.com/actions/starter-workflows/blob/master/LICENSE).

 Please note that this project is released with a [Contributor Code of Conduct](
-https://github.com/actions/.github/blob/main/CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
-
-**At this time we are only accepting new starter workflows for Code Scanning**
-
-### Previous guidelines for new starter workflows.
+https://github.com/actions/.github/blob/master/CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.

 Before merging a new workflow, the following requirements need to be met:

 - Should be as simple as is needed for the service.
 - There are many programming languages and tools out there. Right now we don't have a page that allows for a really large number of workflows, so we do have to be a little choosy about what we accept. Less popular tools or languages might not be accepted.
- Automation and CI workflows should not send data to any 3rd party service except for the purposes of installing dependencies.
- Automation and CI workflows cannot be dependent on a paid service or product.
- We recommend that Actions outside of the `actions` organization be pinned to a specific SHA.
+- Should not send data to any 3rd party service except for the purposes of installing dependencies.
+- Cannot use an Action that isn't in the `actions` organization.
+- Cannot be to a paid service or product.

 Thank you
@@ -1,6 +1,6 @@
 MIT License

-Copyright (c) 2020 GitHub
+Copyright (c) 2019 GitHub

 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -18,5 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE. THIS LICENSE DOES NOT GRANT YOU RIGHTS TO USE ANY CONTRIBUTORS'
-NAME, LOGO, OR TRADEMARKS.
+SOFTWARE.
@@ -13,12 +13,11 @@ These are the workflow files for helping people get started with GitHub Actions.
 **Directory structure:**
 * [ci](ci): solutions for Continuous Integration
 * [automation](automation): solutions for automating workflows.
-* [code-scanning](code-scanning): starter workflows for [Code Scanning](https://github.com/features/security)
 * [icons](icons): svg icons for the relevant template

 Each workflow must be written in YAML and have a `.yml` extension. They also need a corresponding `.properties.json` file that contains extra metadata about the workflow (this is displayed in the GitHub.com UI).

-For example: `ci/django.yml` and `ci/properties/django.properties.json`.
+For example: `ci/python-django.yml` and `ci/python-django.properties.json`.

 **Valid properties:**
 * `name`: the name shown in onboarding
@@ -1,13 +0,0 @@
-name: Greetings
-
-on: [pull_request, issues]
-
-jobs:
-  greeting:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/first-interaction@v1
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        issue-message: 'Message that will be displayed on users first issue'
-        pr-message: 'Message that will be displayed on users first pull request'
@@ -1,19 +0,0 @@
-# This workflow will triage pull requests and apply a label based on the
-# paths that are modified in the pull request.
-#
-# To use this workflow, you will need to set up a .github/labeler.yml
-# file with configuration.  For more information, see:
-# https://github.com/actions/labeler
-
-name: Labeler
-on: [pull_request]
-
-jobs:
-  label:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/labeler@v2
-      with:
-        repo-token: "${{ secrets.GITHUB_TOKEN }}"
@@ -15,6 +15,8 @@ on:
        default: 'World'
        # Input has to be provided for the workflow to run
        required: true
+        # The data type of the input
+        type: string

 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
@@ -27,4 +29,4 @@ jobs:
    steps:
    # Runs a single command using the runners shell
    - name: Send greeting
-      run: echo "Hello ${{ github.event.inputs.name }}"
+      run: echo "Hello ${{ inputs.name }}"
@@ -1,6 +0,0 @@
-{
-    "name": "Greetings",
-    "description": "Greets users who are first time contributors to the repo",
-    "iconName": "octicon smiley",
-    "categories": ["Automation", "SDLC"]
-}
@@ -1,6 +0,0 @@
-{
-    "name": "Labeler",
-    "description": "Labels pull requests based on the files changed",
-    "iconName": "octicon tag",
-    "categories": ["Automation", "SDLC"]
-}
@@ -1,16 +1,24 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
 name: Mark stale issues and pull requests

 on:
  schedule:
-  - cron: "30 1 * * *"
+  - cron: $cron-daily

 jobs:
  stale:

    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write

    steps:
-    - uses: actions/stale@v3
+    - uses: actions/stale@v5
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'Stale issue message'
@@ -13,11 +13,11 @@ jobs:

    steps:
    - name: Checkout
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3

    - name: Set up GNAT toolchain
      run: >
-        sudo apt-get update && 
+        sudo apt-get update &&
        sudo apt-get install gnat gprbuild

    - name: Build
@@ -1,118 +0,0 @@
-# This workflow will build and push a new container image to Alibaba Cloud Container Registry (ACR),
-# and then will deploy it to Alibaba Cloud Container Service for Kubernetes (ACK), when a release is created.
-#
-# To use this workflow, you will need to complete the following set-up steps:
-#
-# 1. Create an ACR repository to store your container images. 
-#    You can use ACR EE instance for more security and better performance.
-#    For instructions see https://www.alibabacloud.com/help/doc-detail/142168.htm
-#
-# 2. Create an ACK cluster to run your containerized application.
-#    You can use ACK Pro cluster for more security and better performance.
-#    For instructions see https://www.alibabacloud.com/help/doc-detail/95108.htm
-#
-# 3. Store your AccessKey pair in GitHub Actions secrets named `ACCESS_KEY_ID` and `ACCESS_KEY_SECRET`.
-#    For instructions on setting up secrets see: https://developer.github.com/actions/managing-workflows/storing-secrets/
-#
-# 4. Change the values for the REGION_ID, REGISTRY, NAMESPACE, IMAGE, ACK_CLUSTER_ID, and ACK_DEPLOYMENT_NAME. 
-#
-
-name: Build and Deploy to ACK
-
-on:
-  release:
-    types: [created]
-
-# Environment variables available to all jobs and steps in this workflow.
-env:
-  REGION_ID: cn-hangzhou
-  REGISTRY: registry.cn-hangzhou.aliyuncs.com
-  NAMESPACE: namespace
-  IMAGE: repo
-  TAG: ${{ github.sha }}
-  ACK_CLUSTER_ID: clusterID
-  ACK_DEPLOYMENT_NAME: nginx-deployment
-
-  ACR_EE_REGISTRY: myregistry.cn-hangzhou.cr.aliyuncs.com
-  ACR_EE_INSTANCE_ID: instanceID
-  ACR_EE_NAMESPACE: namespace
-  ACR_EE_IMAGE: repo
-  ACR_EE_TAG: ${{ github.sha }}
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v2
-    
-    # 1.1 Login to ACR   
-    - name: Login to ACR with the AccessKey pair
-      uses: aliyun/acr-login@v1
-      with:
-        region-id: "${{ env.REGION_ID }}"
-        access-key-id: "${{ secrets.ACCESS_KEY_ID }}"
-        access-key-secret: "${{ secrets.ACCESS_KEY_SECRET }}"
-
-    # 1.2 Buid and push image to ACR   
-    - name: Build and push image to ACR  
-      run: |
-        docker build --tag "$REGISTRY/$NAMESPACE/$IMAGE:$TAG" .  
-        docker push "$REGISTRY/$NAMESPACE/$IMAGE:$TAG"   
- 
-    # 1.3 Scan image in ACR   
-    - name: Scan image in ACR
-      uses: aliyun/acr-scan@v1
-      with:
-        region-id: "${{ env.REGION_ID }}"
-        access-key-id: "${{ secrets.ACCESS_KEY_ID }}"
-        access-key-secret: "${{ secrets.ACCESS_KEY_SECRET }}"
-        repository: "${{ env.NAMESPACE }}/${{ env.IMAGE }}"
-        tag: "${{ env.TAG }}"
-
-    # 2.1 (Optional) Login to ACR EE          
-    - uses: actions/checkout@v2
-    - name: Login to ACR EE with the AccessKey pair
-      uses: aliyun/acr-login@v1
-      with:
-        login-server: "https://${{ env.ACR_EE_REGISTRY }}"
-        region-id: "${{ env.REGION_ID }}"
-        access-key-id: "${{ secrets.ACCESS_KEY_ID }}"
-        access-key-secret: "${{ secrets.ACCESS_KEY_SECRET }}"
-        instance-id: "${{ env.ACR_EE_INSTANCE_ID }}"
-
-    # 2.2 (Optional) Build and push image ACR EE          
-    - name: Build and push image to ACR EE  
-      run: |
-        docker build -t "$ACR_EE_REGISTRY/$ACR_EE_NAMESPACE/$ACR_EE_IMAGE:$TAG" .
-        docker push "$ACR_EE_REGISTRY/$ACR_EE_NAMESPACE/$ACR_EE_IMAGE:$TAG"
-    # 2.3 (Optional) Scan image in ACR EE          
-    - name: Scan image in ACR EE
-      uses: aliyun/acr-scan@v1
-      with:
-        region-id: "${{ env.REGION_ID }}"
-        access-key-id: "${{ secrets.ACCESS_KEY_ID }}"
-        access-key-secret: "${{ secrets.ACCESS_KEY_SECRET }}"
-        instance-id: "${{ env.ACR_EE_INSTANCE_ID }}"
-        repository: "${{ env.ACR_EE_NAMESPACE}}/${{ env.ACR_EE_IMAGE }}"
-        tag: "${{ env.ACR_EE_TAG }}"
-
-    # 3.1 Set ACK context         
-    - name: Set K8s context
-      uses: aliyun/ack-set-context@v1
-      with:
-        access-key-id: "${{ secrets.ACCESS_KEY_ID }}"
-        access-key-secret: "${{ secrets.ACCESS_KEY_SECRET }}"
-        cluster-id: "${{ env.ACK_CLUSTER_ID }}"
-
-    # 3.2 Deploy the image to the ACK cluster
-    - name: Set up Kustomize
-      run: |-
-        curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"  | bash /dev/stdin 3.8.6
-    - name: Deploy
-      run: |-
-        ./kustomize edit set image REGISTRY/NAMESPACE/IMAGE:TAG=$REGISTRY/$NAMESPACE/$IMAGE:$TAG
-        ./kustomize build . | kubectl apply -f -
-        kubectl rollout status deployment/$ACK_DEPLOYMENT_NAME
-        kubectl get services -o wide
@@ -12,11 +12,14 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
-    - name: set up JDK 1.8
-      uses: actions/setup-java@v1
+    - uses: actions/checkout@v3
+    - name: set up JDK 11
+      uses: actions/setup-java@v3
      with:
-        java-version: 1.8
+        java-version: '11'
+        distribution: 'temurin'
+        cache: gradle
+
    - name: Grant execute permission for gradlew
      run: chmod +x gradlew
    - name: Build with Gradle
@@ -1,5 +1,5 @@
 # This workflow will build a Java project with Ant
-# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-ant
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-java-with-ant

 name: Java CI

@@ -15,10 +15,11 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
-    - name: Set up JDK 1.8
-      uses: actions/setup-java@v1
+    - uses: actions/checkout@v3
+    - name: Set up JDK 11
+      uses: actions/setup-java@v3
      with:
-        java-version: 1.8
+        java-version: '11'
+        distribution: 'temurin'
    - name: Build with Ant
      run: ant -noinput -buildfile build.xml
@@ -1,80 +0,0 @@
-# This workflow will build and push a new container image to Amazon ECR,
-# and then will deploy a new task definition to Amazon ECS, when a release is created
-#
-# To use this workflow, you will need to complete the following set-up steps:
-#
-# 1. Create an ECR repository to store your images.
-#    For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`.
-#    Replace the value of `ECR_REPOSITORY` in the workflow below with your repository's name.
-#    Replace the value of `aws-region` in the workflow below with your repository's region.
-#
-# 2. Create an ECS task definition, an ECS cluster, and an ECS service.
-#    For example, follow the Getting Started guide on the ECS console:
-#      https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun
-#    Replace the values for `service` and `cluster` in the workflow below with your service and cluster names.
-#
-# 3. Store your ECS task definition as a JSON file in your repository.
-#    The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`.
-#    Replace the value of `task-definition` in the workflow below with your JSON file's name.
-#    Replace the value of `container-name` in the workflow below with the name of the container
-#    in the `containerDefinitions` section of the task definition.
-#
-# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
-#    See the documentation for each action used below for the recommended IAM policies for this IAM user,
-#    and best practices on handling the access key credentials.
-
-on:
-  release:
-    types: [created]
-
-name: Deploy to Amazon ECS
-
-jobs:
-  deploy:
-    name: Deploy
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v2
-
-    - name: Configure AWS credentials
-      uses: aws-actions/configure-aws-credentials@v1
-      with:
-        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
-        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-        aws-region: us-east-2
-
-    - name: Login to Amazon ECR
-      id: login-ecr
-      uses: aws-actions/amazon-ecr-login@v1
-
-    - name: Build, tag, and push image to Amazon ECR
-      id: build-image
-      env:
-        ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
-        ECR_REPOSITORY: my-ecr-repo
-        IMAGE_TAG: ${{ github.sha }}
-      run: |
-        # Build a docker container and
-        # push it to ECR so that it can
-        # be deployed to ECS.
-        docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
-        docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
-        echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG"
-
-    - name: Fill in the new image ID in the Amazon ECS task definition
-      id: task-def
-      uses: aws-actions/amazon-ecs-render-task-definition@v1
-      with:
-        task-definition: task-definition.json
-        container-name: sample-app
-        image: ${{ steps.build-image.outputs.image }}
-
-    - name: Deploy Amazon ECS task definition
-      uses: aws-actions/amazon-ecs-deploy-task-definition@v1
-      with:
-        task-definition: ${{ steps.task-def.outputs.task-definition }}
-        service: sample-app-service
-        cluster: default
-        wait-for-service-stability: true
@@ -1,50 +0,0 @@
-# This workflow will build and push a node.js application to an Azure Web App when a release is created.
-#
-# This workflow assumes you have already created the target Azure App Service web app.
-# For instructions see https://docs.microsoft.com/azure/app-service/app-service-plan-manage#create-an-app-service-plan
-#
-# To configure this workflow:
-#
-# 1. For Linux apps, add an app setting called WEBSITE_WEBDEPLOY_USE_SCM and set it to true in your app **before downloading the file**.
-#      For more instructions see: https://docs.microsoft.com/azure/app-service/configure-common#configure-app-settings
-#
-# 2. Set up a secret in your repository named AZURE_WEBAPP_PUBLISH_PROFILE with the value of your Azure publish profile.
-#    For instructions on obtaining the publish profile see: https://docs.microsoft.com/azure/app-service/deploy-github-actions#configure-the-github-secret
-#
-# 3. Change the values for the AZURE_WEBAPP_NAME, AZURE_WEBAPP_PACKAGE_PATH and NODE_VERSION environment variables  (below).
-#
-# For more information on GitHub Actions for Azure, refer to https://github.com/Azure/Actions
-# For more samples to get started with GitHub Action workflows to deploy to Azure, refer to https://github.com/Azure/actions-workflow-samples
-on:
-  release:
-    types: [created]
-
-env:
-  AZURE_WEBAPP_NAME: your-app-name    # set this to your application's name
-  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
-  NODE_VERSION: '10.x'                # set this to the node version to use
-
-jobs:
-  build-and-deploy:
-    name: Build and Deploy
-    runs-on: ubuntu-latest
-    environment: production
-    steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ env.NODE_VERSION }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ env.NODE_VERSION }}
-    - name: npm install, build, and test
-      run: |
-        # Build and test the project, then
-        # deploy to Azure Web App.
-        npm install
-        npm run build --if-present
-        npm run test --if-present
-    - name: 'Deploy to Azure WebApp'
-      uses: azure/webapps-deploy@v2
-      with:
-        app-name: ${{ env.AZURE_WEBAPP_NAME }}
-        publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}
-        package: ${{ env.AZURE_WEBAPP_PACKAGE_PATH }}
@@ -2,7 +2,7 @@

 name: CI

-# Controls when the action will run. 
+# Controls when the workflow will run
 on:
  # Triggers the workflow on push or pull request events but only for the $default-branch branch
  push:
@@ -23,7 +23,7 @@ jobs:
    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3

      # Runs a single command using the runners shell
      - name: Run a one-line script
@@ -12,7 +12,7 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: configure
      run: ./configure
    - name: make
@@ -12,7 +12,7 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Install dependencies
      run: lein deps
    - name: Run tests
@@ -0,0 +1,75 @@
+# This starter workflow is for a CMake project running on multiple platforms. There is a different starter workflow if you just want a single platform.
+# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-single-platform.yml
+name: CMake on multiple platforms
+
+on:
+  push:
+    branches: [ $default-branch ]
+  pull_request:
+    branches: [ $default-branch ]
+
+jobs:
+  build:
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      # Set fail-fast to false to ensure that feedback is delivered for all matrix combinations. Consider changing this to true when your workflow is stable.
+      fail-fast: false
+
+      # Set up a matrix to run the following 3 configurations:
+      # 1. <Windows, Release, latest MSVC compiler toolchain on the default runner image, default generator>
+      # 2. <Linux, Release, latest GCC compiler toolchain on the default runner image, default generator>
+      # 3. <Linux, Release, latest Clang compiler toolchain on the default runner image, default generator>
+      #
+      # To add more build types (Release, Debug, RelWithDebInfo, etc.) customize the build_type list.
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+        build_type: [Release]
+        c_compiler: [gcc, clang, cl]
+        include:
+          - os: windows-latest
+            c_compiler: cl
+            cpp_compiler: cl
+          - os: ubuntu-latest
+            c_compiler: gcc
+            cpp_compiler: g++
+          - os: ubuntu-latest
+            c_compiler: clang
+            cpp_compiler: clang++
+        exclude:
+          - os: windows-latest
+            c_compiler: gcc
+          - os: windows-latest
+            c_compiler: clang
+          - os: ubuntu-latest
+            c_compiler: cl
+
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: Set reusable strings
+      # Turn repeated input strings (such as the build output directory) into step outputs. These step outputs can be used throughout the workflow file.
+      id: strings
+      shell: bash
+      run: |
+        echo "build-output-dir=${{ github.workspace }}/build" >> "$GITHUB_OUTPUT"
+
+    - name: Configure CMake
+      # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
+      # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
+      run: >
+        cmake -B ${{ steps.strings.outputs.build-output-dir }}
+        -DCMAKE_CXX_COMPILER=${{ matrix.cpp_compiler }}
+        -DCMAKE_C_COMPILER=${{ matrix.c_compiler }}
+        -DCMAKE_BUILD_TYPE=${{ matrix.build_type }}
+        -S ${{ github.workspace }}
+
+    - name: Build
+      # Build your program with the given configuration. Note that --config is needed because the default Windows generator is a multi-config generator (Visual Studio generator).
+      run: cmake --build ${{ steps.strings.outputs.build-output-dir }} --config ${{ matrix.build_type }}
+
+    - name: Test
+      working-directory: ${{ steps.strings.outputs.build-output-dir }}
+      # Execute tests defined by the CMake configuration. Note that --build-config is needed because the default Windows generator is a multi-config generator (Visual Studio generator).
+      # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
+      run: ctest --build-config ${{ matrix.build_type }}
@@ -0,0 +1,39 @@
+# This starter workflow is for a CMake project running on a single platform. There is a different starter workflow if you need cross-platform coverage.
+# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-multi-platform.yml
+name: CMake on a single platform
+
+on:
+  push:
+    branches: [ $default-branch ]
+  pull_request:
+    branches: [ $default-branch ]
+
+env:
+  # Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.)
+  BUILD_TYPE: Release
+
+jobs:
+  build:
+    # The CMake configure and build commands are platform agnostic and should work equally well on Windows or Mac.
+    # You can convert this to a matrix build if you need cross-platform coverage.
+    # See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: Configure CMake
+      # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
+      # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
+      run: cmake -B ${{github.workspace}}/build -DCMAKE_BUILD_TYPE=${{env.BUILD_TYPE}}
+
+    - name: Build
+      # Build your program with the given configuration
+      run: cmake --build ${{github.workspace}}/build --config ${{env.BUILD_TYPE}}
+
+    - name: Test
+      working-directory: ${{github.workspace}}/build
+      # Execute tests defined by the CMake configuration.
+      # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
+      run: ctest -C ${{env.BUILD_TYPE}}
+
@@ -1,46 +0,0 @@
-name: CMake
-
-on: [push]
-
-env:
-  # Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.)
-  BUILD_TYPE: Release
-
-jobs:
-  build:
-    # The CMake configure and build commands are platform agnostic and should work equally
-    # well on Windows or Mac.  You can convert this to a matrix build if you need
-    # cross-platform coverage.
-    # See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-
-    - name: Create Build Environment
-      # Some projects don't allow in-source building, so create a separate build directory
-      # We'll use this as our working directory for all subsequent commands
-      run: cmake -E make_directory ${{github.workspace}}/build
-
-    - name: Configure CMake
-      # Use a bash shell so we can use the same syntax for environment variable
-      # access regardless of the host operating system
-      shell: bash
-      working-directory: ${{github.workspace}}/build
-      # Note the current convention is to use the -S and -B options here to specify source 
-      # and build directories, but this is only available with CMake 3.13 and higher.  
-      # The CMake binaries on the Github Actions machines are (as of this writing) 3.12
-      run: cmake $GITHUB_WORKSPACE -DCMAKE_BUILD_TYPE=$BUILD_TYPE
-
-    - name: Build
-      working-directory: ${{github.workspace}}/build
-      shell: bash
-      # Execute the build.  You can specify a specific target with "--target <NAME>"
-      run: cmake --build . --config $BUILD_TYPE
-
-    - name: Test
-      working-directory: ${{github.workspace}}/build
-      shell: bash
-      # Execute tests defined by the CMake configuration.  
-      # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
-      run: ctest -C $BUILD_TYPE
@@ -15,7 +15,7 @@ jobs:
      image: crystallang/crystal

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Install dependencies
      run: shards install
    - name: Run tests
@@ -1,29 +0,0 @@
-# This workflow uses actions that are not certified by GitHub.
-# They are provided by a third-party and are governed by
-# separate terms of service, privacy policy, and support
-# documentation.
-name: D
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - uses: dlang-community/setup-dlang@4c99aa991ce7d19dd3064de0a4f2f6b2f152e2d7
-
-    - name: 'Build & Test'
-      run: |
-        # Build the project, with its main file included, without unittests
-        dub build --compiler=$DC
-        # Build and run tests, as defined by `unittest` configuration
-        # In this mode, `mainSourceFile` is excluded and `version (unittest)` are included
-        # See https://dub.pm/package-format-json.html#configurations
-        dub test --compiler=$DC
@@ -1,41 +0,0 @@
-name: Dart
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-
-    # Note that this workflow uses the latest stable version of the Dart SDK.
-    # Docker images for other release channels - like dev and beta - are also
-    # available. See https://hub.docker.com/r/google/dart/ for the available
-    # images.
-    container:
-      image:  google/dart:latest
-
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Print Dart SDK version
-        run: dart --version
-
-      - name: Install dependencies
-        run: dart pub get
-
-      # Uncomment this step to verify the use of 'dart format' on each commit.
-      # - name: Verify formatting
-      #   run: dart format --output=none --set-exit-if-changed .
-
-      # Consider passing '--fatal-infos' for slightly stricter analysis.
-      - name: Analyze project source
-        run: dart analyze
-
-      # Your project will need to have tests in test/ and a dependency on
-      # package:test for this step to succeed. Note that Flutter projects will
-      # want to change this to 'flutter test'.
-      - name: Run tests
-        run: dart test
@@ -1,39 +0,0 @@
-# This workflow uses actions that are not certified by GitHub.
-# They are provided by a third-party and are governed by
-# separate terms of service, privacy policy, and support
-# documentation.
-
-# This workflow will install Deno and run tests across stable and nightly builds on Windows, Ubuntu and macOS.
-# For more information see: https://github.com/denolib/setup-deno
-
-name: Deno
-
-on:
-  push:
-    branches: [$default-branch]
-  pull_request:
-    branches: [$default-branch]
-
-jobs:
-  test:
-    runs-on: ${{ matrix.os }} # runs a test on Ubuntu, Windows and macOS
-
-    strategy:
-      matrix:
-        deno: ["v1.x", "nightly"]
-        os: [macOS-latest, windows-latest, ubuntu-latest]
-
-    steps:
-      - name: Setup repo
-        uses: actions/checkout@v2
-
-      - name: Setup Deno
-        uses: denolib/setup-deno@c7d7968ad4a59c159a777f79adddad6872ee8d96
-        with:
-          deno-version: ${{ matrix.deno }} # tests across multiple Deno versions
-
-      - name: Cache Dependencies
-        run: deno cache deps.ts
-
-      - name: Run Tests
-        run: deno test -A --unstable
@@ -16,9 +16,9 @@ jobs:
        python-version: [3.7, 3.8, 3.9]

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
+      uses: actions/setup-python@v3
      with:
        python-version: ${{ matrix.python-version }}
    - name: Install Dependencies
@@ -13,6 +13,6 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Build the Docker image
      run: docker build . --file Dockerfile --tag my-image-name:$(date +%s)
@@ -1,76 +0,0 @@
-name: Docker
-
-on:
-  push:
-    # Publish `$default-branch` as Docker `latest` image.
-    branches:
-      - $default-branch
-
-    # Publish `v1.2.3` tags as releases.
-    tags:
-      - v*
-
-  # Run tests for any PRs.
-  pull_request:
-
-env:
-  # TODO: Change variable to your image's name.
-  IMAGE_NAME: image
-
-jobs:
-  # Run tests.
-  # See also https://docs.docker.com/docker-hub/builds/automated-testing/
-  test:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Run tests
-        run: |
-          if [ -f docker-compose.test.yml ]; then
-            docker-compose --file docker-compose.test.yml build
-            docker-compose --file docker-compose.test.yml run sut
-          else
-            docker build . --file Dockerfile
-          fi
-
-  # Push image to GitHub Packages.
-  # See also https://docs.docker.com/docker-hub/builds/
-  push:
-    # Ensure test job passes before pushing image.
-    needs: test
-
-    runs-on: ubuntu-latest
-    if: github.event_name == 'push'
-
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Build image
-        run: docker build . --file Dockerfile --tag $IMAGE_NAME
-
-      - name: Log into registry
-        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login docker.pkg.github.com -u ${{ github.actor }} --password-stdin
-
-      - name: Push image
-        run: |
-          IMAGE_ID=docker.pkg.github.com/${{ github.repository }}/$IMAGE_NAME
-
-          # Change all uppercase to lowercase
-          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
-
-          # Strip git ref prefix from version
-          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
-
-          # Strip "v" prefix from tag name
-          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
-
-          # Use Docker `latest` tag convention
-          [ "$VERSION" == "$default-branch" ] && VERSION=latest
-
-          echo IMAGE_ID=$IMAGE_ID
-          echo VERSION=$VERSION
-
-          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
-          docker push $IMAGE_ID:$VERSION
@@ -1,115 +0,0 @@
-# This workflow uses actions that are not certified by GitHub.
-# They are provided by a third-party and are governed by
-# separate terms of service, privacy policy, and support
-# documentation.
-
-# This workflow will build, test, sign and package a WPF or Windows Forms desktop application
-# built on .NET Core.
-# To learn how to migrate your existing application to .NET Core,
-# refer to https://docs.microsoft.com/en-us/dotnet/desktop-wpf/migration/convert-project-from-net-framework
-#
-# To configure this workflow:
-#
-# 1. Configure environment variables
-# GitHub sets default environment variables for every workflow run.
-# Replace the variables relative to your project in the "env" section below.
-#
-# 2. Signing
-# Generate a signing certificate in the Windows Application
-# Packaging Project or add an existing signing certificate to the project.
-# Next, use PowerShell to encode the .pfx file using Base64 encoding
-# by running the following Powershell script to generate the output string:
-#
-# $pfx_cert = Get-Content '.\SigningCertificate.pfx' -Encoding Byte
-# [System.Convert]::ToBase64String($pfx_cert) | Out-File 'SigningCertificate_Encoded.txt'
-#
-# Open the output file, SigningCertificate_Encoded.txt, and copy the
-# string inside. Then, add the string to the repo as a GitHub secret
-# and name it "Base64_Encoded_Pfx."
-# For more information on how to configure your signing certificate for
-# this workflow, refer to https://github.com/microsoft/github-actions-for-desktop-apps#signing
-#
-# Finally, add the signing certificate password to the repo as a secret and name it "Pfx_Key".
-# See "Build the Windows Application Packaging project" below to see how the secret is used.
-#
-# For more information on GitHub Actions, refer to https://github.com/features/actions
-# For a complete CI/CD sample to get started with GitHub Action workflows for Desktop Applications,
-# refer to https://github.com/microsoft/github-actions-for-desktop-apps
-
-name: .NET Core Desktop
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-
-  build:
-
-    strategy:
-      matrix:
-        configuration: [Debug, Release]
-
-    runs-on: windows-latest  # For a list of available runner types, refer to
-                             # https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on
-
-    env:
-      Solution_Name: your-solution-name                         # Replace with your solution name, i.e. MyWpfApp.sln.
-      Test_Project_Path: your-test-project-path                 # Replace with the path to your test project, i.e. MyWpfApp.Tests\MyWpfApp.Tests.csproj.
-      Wap_Project_Directory: your-wap-project-directory-name    # Replace with the Wap project directory relative to the solution, i.e. MyWpfApp.Package.
-      Wap_Project_Path: your-wap-project-path                   # Replace with the path to your Wap project, i.e. MyWpf.App.Package\MyWpfApp.Package.wapproj.
-
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v2
-      with:
-        fetch-depth: 0
-
-    # Install the .NET Core workload
-    - name: Install .NET Core
-      uses: actions/setup-dotnet@v1
-      with:
-        dotnet-version: 5.0.x
-
-    # Add  MSBuild to the PATH: https://github.com/microsoft/setup-msbuild
-    - name: Setup MSBuild.exe
-      uses: microsoft/setup-msbuild@2008f912f56e61277eefaac6d1888b750582aa16
-
-    # Execute all unit tests in the solution
-    - name: Execute unit tests
-      run: dotnet test
-
-    # Restore the application to populate the obj folder with RuntimeIdentifiers
-    - name: Restore the application
-      run: msbuild $env:Solution_Name /t:Restore /p:Configuration=$env:Configuration
-      env:
-        Configuration: ${{ matrix.configuration }}
-
-    # Decode the base 64 encoded pfx and save the Signing_Certificate
-    - name: Decode the pfx
-      run: |
-        $pfx_cert_byte = [System.Convert]::FromBase64String("${{ secrets.Base64_Encoded_Pfx }}")
-        $certificatePath = Join-Path -Path $env:Wap_Project_Directory -ChildPath GitHubActionsWorkflow.pfx
-        [IO.File]::WriteAllBytes("$certificatePath", $pfx_cert_byte)
-
-    # Create the app package by building and packaging the Windows Application Packaging project
-    - name: Create the app package
-      run: msbuild $env:Wap_Project_Path /p:Configuration=$env:Configuration /p:UapAppxPackageBuildMode=$env:Appx_Package_Build_Mode /p:AppxBundle=$env:Appx_Bundle /p:PackageCertificateKeyFile=GitHubActionsWorkflow.pfx /p:PackageCertificatePassword=${{ secrets.Pfx_Key }}
-      env:
-        Appx_Bundle: Always
-        Appx_Bundle_Platforms: x86|x64
-        Appx_Package_Build_Mode: StoreUpload
-        Configuration: ${{ matrix.configuration }}
-
-    # Remove the pfx
-    - name: Remove the pfx
-      run: Remove-Item -path $env:Wap_Project_Directory\$env:Signing_Certificate
-
-    # Upload the MSIX package: https://github.com/marketplace/actions/upload-artifact
-    - name: Upload build artifacts
-      uses: actions/upload-artifact@v2
-      with:
-        name: MSIX Package
-        path: ${{ env.Wap_Project_Directory }}\AppPackages
@@ -1,3 +1,6 @@
+# This workflow will build a .NET project
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-net
+
 name: .NET

 on:
@@ -12,11 +15,11 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v4
    - name: Setup .NET
-      uses: actions/setup-dotnet@v1
+      uses: actions/setup-dotnet@v4
      with:
-        dotnet-version: 5.0.x
+        dotnet-version: 8.0.x
    - name: Restore dependencies
      run: dotnet restore
    - name: Build
@@ -1,31 +0,0 @@
-name: Elixir CI
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    name: Build and test
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Elixir
-      uses: actions/setup-elixir@v1
-      with:
-        elixir-version: '1.10.3' # Define the elixir version [required]
-        otp-version: '22.3' # Define the OTP version [required]
-    - name: Restore dependencies cache
-      uses: actions/cache@v2
-      with:
-        path: deps
-        key: ${{ runner.os }}-mix-${{ hashFiles('**/mix.lock') }}
-        restore-keys: ${{ runner.os }}-mix-
-    - name: Install dependencies
-      run: mix deps.get
-    - name: Run tests
-      run: mix test
@@ -6,6 +6,9 @@ on:
  pull_request:
    branches: [ $default-branch ]

+permissions:
+  contents: read
+
 jobs:

  build:
@@ -16,7 +19,7 @@ jobs:
      image: erlang:22.0.7

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Compile
      run: rebar3 compile
    - name: Run tests
@@ -1,42 +0,0 @@
-name: Ruby Gem
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-    name: Build + Publish
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: actions/setup-ruby@v1
-      with:
-        ruby-version: 2.6.x
-
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
-
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
@@ -0,0 +1,66 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# This workflow lets you generate SLSA provenance file for your project.
+# The generation satisfies level 3 for the provenance requirements - see https://slsa.dev/spec/v0.1/requirements
+# The project is an initiative of the OpenSSF (openssf.org) and is developed at
+# https://github.com/slsa-framework/slsa-github-generator.
+# The provenance file can be verified using https://github.com/slsa-framework/slsa-verifier.
+# For more information about SLSA and how it improves the supply-chain, visit slsa.dev.
+
+name: SLSA generic generator
+on:
+  workflow_dispatch:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    outputs:
+      digests: ${{ steps.hash.outputs.digests }}
+
+    steps:
+      - uses: actions/checkout@v3
+
+      # ========================================================
+      #
+      # Step 1: Build your artifacts.
+      #
+      # ========================================================
+      - name: Build artifacts
+        run: |
+            # These are some amazing artifacts.
+            echo "artifact1" > artifact1
+            echo "artifact2" > artifact2
+
+      # ========================================================
+      #
+      # Step 2: Add a step to generate the provenance subjects
+      #         as shown below. Update the sha256 sum arguments
+      #         to include all binaries that you generate
+      #         provenance for.
+      #
+      # ========================================================
+      - name: Generate subject for provenance
+        id: hash
+        run: |
+          set -euo pipefail
+
+          # List the artifacts the provenance will refer to.
+          files=$(ls artifact*)
+          # Generate the subjects (base64 encoded).
+          echo "hashes=$(sha256sum $files | base64 -w0)" >> "${GITHUB_OUTPUT}"
+
+  provenance:
+    needs: [build]
+    permissions:
+      actions: read   # To read the workflow path.
+      id-token: write # To sign the provenance.
+      contents: write # To add assets to a release.
+    uses: slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@v1.4.0
+    with:
+      base64-subjects: "${{ needs.build.outputs.digests }}"
+      upload-assets: true # Optional: Upload to a new release
@@ -0,0 +1,38 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# This workflow lets you compile your Go project using a SLSA3 compliant builder.
+# This workflow will generate a so-called "provenance" file describing the steps
+# that were performed to generate the final binary.
+# The project is an initiative of the OpenSSF (openssf.org) and is developed at
+# https://github.com/slsa-framework/slsa-github-generator.
+# The provenance file can be verified using https://github.com/slsa-framework/slsa-verifier.
+# For more information about SLSA and how it improves the supply-chain, visit slsa.dev.
+
+name: SLSA Go releaser
+on:
+  workflow_dispatch:
+  release:
+    types: [created]
+
+permissions: read-all
+
+jobs:
+  # ========================================================================================================================================
+  #     Prerequesite: Create a .slsa-goreleaser.yml in the root directory of your project.
+  #       See format in https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/go/README.md#configuration-file
+  #=========================================================================================================================================
+  build:
+    permissions:
+      id-token: write # To sign.
+      contents: write # To upload release assets.
+      actions: read   # To read workflow path.
+    uses: slsa-framework/slsa-github-generator/.github/workflows/builder_go_slsa3.yml@v1.4.0
+    with:
+      go-version: 1.17
+      # =============================================================================================================
+      #     Optional: For more options, see https://github.com/slsa-framework/slsa-github-generator#golang-projects
+      # =============================================================================================================
+
@@ -1,3 +1,6 @@
+# This workflow will build a golang project
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-go
+
 name: Go

 on:
@@ -11,12 +14,12 @@ jobs:
  build:
    runs-on: ubuntu-latest
    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3

    - name: Set up Go
-      uses: actions/setup-go@v2
+      uses: actions/setup-go@v4
      with:
-        go-version: 1.15
+        go-version: '1.20'

    - name: Build
      run: go build -v ./...
@@ -1,79 +0,0 @@
-# This workflow will build a docker container, publish it to Google Container Registry, and deploy it to GKE when a release is created
-#
-# To configure this workflow:
-#
-# 1. Ensure that your repository contains the necessary configuration for your Google Kubernetes Engine cluster, including deployment.yml, kustomization.yml, service.yml, etc.
-#
-# 2. Set up secrets in your workspace: GKE_PROJECT with the name of the project and GKE_SA_KEY with the Base64 encoded JSON service account key (https://github.com/GoogleCloudPlatform/github-actions/tree/docs/service-account-key/setup-gcloud#inputs).
-#
-# 3. Change the values for the GKE_ZONE, GKE_CLUSTER, IMAGE, and DEPLOYMENT_NAME environment variables (below).
-#
-# For more support on how to run the workflow, please visit https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke
-
-name: Build and Deploy to GKE
-
-on:
-  release:
-    types: [created]
-
-env:
-  PROJECT_ID: ${{ secrets.GKE_PROJECT }}
-  GKE_CLUSTER: cluster-1    # TODO: update to cluster name
-  GKE_ZONE: us-central1-c   # TODO: update to cluster zone
-  DEPLOYMENT_NAME: gke-test # TODO: update to deployment name
-  IMAGE: static-site
-
-jobs:
-  setup-build-publish-deploy:
-    name: Setup, Build, Publish, and Deploy
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v2
-
-    # Setup gcloud CLI
-    - uses: google-github-actions/setup-gcloud@v0.2.0
-      with:
-        service_account_key: ${{ secrets.GKE_SA_KEY }}
-        project_id: ${{ secrets.GKE_PROJECT }}
-
-    # Configure Docker to use the gcloud command-line tool as a credential
-    # helper for authentication
-    - run: |-
-        gcloud --quiet auth configure-docker
-
-    # Get the GKE credentials so we can deploy to the cluster
-    - uses: google-github-actions/get-gke-credentials@v0.2.1
-      with:
-        cluster_name: ${{ env.GKE_CLUSTER }}
-        location: ${{ env.GKE_ZONE }}
-        credentials: ${{ secrets.GKE_SA_KEY }}
-
-    # Build the Docker image
-    - name: Build
-      run: |-
-        docker build \
-          --tag "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" \
-          --build-arg GITHUB_SHA="$GITHUB_SHA" \
-          --build-arg GITHUB_REF="$GITHUB_REF" \
-          .
-
-    # Push the Docker image to Google Container Registry
-    - name: Publish
-      run: |-
-        docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA"
-
-    # Set up kustomize
-    - name: Set up Kustomize
-      run: |-
-        curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64
-        chmod u+x ./kustomize
-
-    # Deploy the Docker image to the GKE cluster
-    - name: Deploy
-      run: |-
-        ./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA
-        ./kustomize build . | kubectl apply -f -
-        kubectl rollout status deployment/$DEPLOYMENT_NAME
-        kubectl get services -o wide
@@ -1,33 +0,0 @@
-# This workflow will build a package using Gradle and then publish it to GitHub packages when a release is created
-# For more information see: https://github.com/actions/setup-java#publishing-using-gradle
-
-name: Gradle Package
-
-on:
-  release:
-    types: [created]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up JDK 1.8
-      uses: actions/setup-java@v1
-      with:
-        java-version: 1.8
-        server-id: github # Value of the distributionManagement/repository/id field of the pom.xml
-        settings-path: ${{ github.workspace }} # location for the settings.xml file
-
-    - name: Build with Gradle
-      run: gradle build
-
-    # The USERNAME and TOKEN need to correspond to the credentials environment variables used in
-    # the publishing section of your build.gradle
-    - name: Publish to GitHub Packages
-      run: gradle publish
-      env:
-        USERNAME: ${{ github.actor }}
-        TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -1,26 +0,0 @@
-# This workflow will build a Java project with Gradle
-# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-gradle
-
-name: Java CI with Gradle
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up JDK 1.8
-      uses: actions/setup-java@v1
-      with:
-        java-version: 1.8
-    - name: Grant execute permission for gradlew
-      run: chmod +x gradlew
-    - name: Build with Gradle
-      run: ./gradlew build
@@ -1,40 +0,0 @@
-name: Haskell CI
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-haskell@v1
-      with:
-        ghc-version: '8.10.3'
-        cabal-version: '3.2'
-
-    - name: Cache
-      uses: actions/cache@v1
-      env:
-        cache-name: cache-cabal
-      with:
-        path: ~/.cabal
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/*.cabal') }}-${{ hashFiles('**/cabal.project') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
-
-    - name: Install dependencies
-      run: |
-        cabal update
-        cabal build --only-dependencies --enable-tests --enable-benchmarks
-    - name: Build
-      run: cabal build --enable-tests --enable-benchmarks all
-    - name: Run tests
-      run: cabal test all
@@ -1,74 +0,0 @@
-# This workflow will build a docker container, publish it to IBM Container Registry, and deploy it to IKS when a release is created
-#
-# To configure this workflow:
-#
-# 1. Ensure that your repository contains a Dockerfile
-# 2. Setup secrets in your repository by going to settings: Create ICR_NAMESPACE and IBM_CLOUD_API_KEY
-# 3. Change the values for the IBM_CLOUD_REGION, REGISTRY_HOSTNAME, IMAGE_NAME, IKS_CLUSTER, DEPLOYMENT_NAME, and PORT
-
-name: Build and Deploy to IKS
-
-on:
-  release:
-    types: [created]
-
-# Environment variables available to all jobs and steps in this workflow
-env:
-  GITHUB_SHA: ${{ github.sha }}
-  IBM_CLOUD_API_KEY: ${{ secrets.IBM_CLOUD_API_KEY }}
-  IBM_CLOUD_REGION: us-south
-  ICR_NAMESPACE: ${{ secrets.ICR_NAMESPACE }}
-  REGISTRY_HOSTNAME: us.icr.io
-  IMAGE_NAME: iks-test
-  IKS_CLUSTER: example-iks-cluster-name-or-id
-  DEPLOYMENT_NAME: iks-test
-  PORT: 5001
-
-jobs:
-  setup-build-publish-deploy:
-    name: Setup, Build, Publish, and Deploy
-    runs-on: ubuntu-latest
-    steps:
-
-    - name: Checkout
-      uses: actions/checkout@v2
-
-    # Download and Install IBM Cloud CLI
-    - name: Install IBM Cloud CLI
-      run: |
-        curl -fsSL https://clis.cloud.ibm.com/install/linux | sh
-        ibmcloud --version
-        ibmcloud config --check-version=false
-        ibmcloud plugin install -f kubernetes-service
-        ibmcloud plugin install -f container-registry
-
-    # Authenticate with IBM Cloud CLI
-    - name: Authenticate with IBM Cloud CLI
-      run: |
-        ibmcloud login --apikey "${IBM_CLOUD_API_KEY}" -r "${IBM_CLOUD_REGION}" -g default
-        ibmcloud cr region-set "${IBM_CLOUD_REGION}"
-        ibmcloud cr login
-
-    # Build the Docker image
-    - name: Build with Docker
-      run: |
-        docker build -t "$REGISTRY_HOSTNAME"/"$ICR_NAMESPACE"/"$IMAGE_NAME":"$GITHUB_SHA" \
-          --build-arg GITHUB_SHA="$GITHUB_SHA" \
-          --build-arg GITHUB_REF="$GITHUB_REF" .
-
-    # Push the image to IBM Container Registry
-    - name: Push the image to ICR
-      run: |
-        docker push $REGISTRY_HOSTNAME/$ICR_NAMESPACE/$IMAGE_NAME:$GITHUB_SHA
-
-    # Deploy the Docker image to the IKS cluster
-    - name: Deploy to IKS
-      run: |
-        ibmcloud ks cluster config --cluster $IKS_CLUSTER
-        kubectl config current-context
-        kubectl create deployment $DEPLOYMENT_NAME --image=$REGISTRY_HOSTNAME/$ICR_NAMESPACE/$IMAGE_NAME:$GITHUB_SHA --dry-run -o yaml > deployment.yaml
-        kubectl apply -f deployment.yaml
-        kubectl rollout status deployment/$DEPLOYMENT_NAME
-        kubectl create service loadbalancer $DEPLOYMENT_NAME --tcp=80:$PORT --dry-run -o yaml > service.yaml
-        kubectl apply -f service.yaml
-        kubectl get services -o wide
@@ -13,7 +13,7 @@ jobs:

    steps:
      - name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
      - name: Set Default Scheme
        run: |
          scheme_list=$(xcodebuild -list -json | tr -d "\n")
@@ -25,7 +25,8 @@ jobs:
          scheme: ${{ 'default' }}
          platform: ${{ 'iOS Simulator' }}
        run: |
-          device=`instruments -s -devices | grep -oE 'iPhone.*?[^\(]+' | head -1 | awk '{$1=$1;print}'`
+          # xcrun xctrace returns via stderr, not the expected stdout (see https://developer.apple.com/forums/thread/663959)
+          device=`xcrun xctrace list devices 2>&1 | grep -oE 'iPhone.*?[^\(]+' | head -1 | awk '{$1=$1;print}' | sed -e "s/ Simulator$//"`
          if [ $scheme = default ]; then scheme=$(cat default); fi
          if [ "`ls -A | grep -i \\.xcworkspace\$`" ]; then filetype_parameter="workspace" && file_to_build="`ls -A | grep -i \\.xcworkspace\$`"; else filetype_parameter="project" && file_to_build="`ls -A | grep -i \\.xcodeproj\$`"; fi
          file_to_build=`echo $file_to_build | awk '{$1=$1;print}'`
@@ -35,7 +36,8 @@ jobs:
          scheme: ${{ 'default' }}
          platform: ${{ 'iOS Simulator' }}
        run: |
-          device=`instruments -s -devices | grep -oE 'iPhone.*?[^\(]+' | head -1 | awk '{$1=$1;print}'`
+          # xcrun xctrace returns via stderr, not the expected stdout (see https://developer.apple.com/forums/thread/663959)
+          device=`xcrun xctrace list devices 2>&1 | grep -oE 'iPhone.*?[^\(]+' | head -1 | awk '{$1=$1;print}' | sed -e "s/ Simulator$//"`
          if [ $scheme = default ]; then scheme=$(cat default); fi
          if [ "`ls -A | grep -i \\.xcworkspace\$`" ]; then filetype_parameter="workspace" && file_to_build="`ls -A | grep -i \\.xcworkspace\$`"; else filetype_parameter="project" && file_to_build="`ls -A | grep -i \\.xcodeproj\$`"; fi
          file_to_build=`echo $file_to_build | awk '{$1=$1;print}'`
@@ -12,9 +12,9 @@ jobs:
    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Build the site in the jekyll/builder container
      run: |
        docker run \
        -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
-        jekyll/builder:latest /bin/bash -c "chmod 777 /srv/jekyll && jekyll build --future"
+        jekyll/builder:latest /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future"
@@ -1,35 +0,0 @@
-name: Laravel
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  laravel-tests:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: shivammathur/setup-php@b7d1d9c9a92d8d8463ce36d7f60da34d461724f8
-      with:
-        php-version: '8.0'
-    - uses: actions/checkout@v2
-    - name: Copy .env
-      run: php -r "file_exists('.env') || copy('.env.example', '.env');"
-    - name: Install Dependencies
-      run: composer install -q --no-ansi --no-interaction --no-scripts --no-progress --prefer-dist
-    - name: Generate key
-      run: php artisan key:generate
-    - name: Directory Permissions
-      run: chmod -R 777 storage bootstrap/cache
-    - name: Create Database
-      run: |
-        mkdir -p database
-        touch database/database.sqlite
-    - name: Execute tests (Unit and Feature tests) via PHPUnit
-      env:
-        DB_CONNECTION: sqlite
-        DB_DATABASE: database/database.sqlite
-      run: vendor/bin/phpunit
@@ -0,0 +1,27 @@
+name: Makefile CI
+
+on:
+  push:
+    branches: [ $default-branch ]
+  pull_request:
+    branches: [ $default-branch ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: configure
+      run: ./configure
+
+    - name: Install dependencies
+      run: make
+
+    - name: Run check
+      run: make check
+
+    - name: Run distcheck
+      run: make distcheck
@@ -1,5 +1,5 @@
 # This workflow will build a package using Maven and then publish it to GitHub packages when a release is created
-# For more information see: https://github.com/actions/setup-java#apache-maven-with-a-settings-path
+# For more information see: https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#apache-maven-with-a-settings-path

 name: Maven Package

@@ -11,13 +11,17 @@ jobs:
  build:

    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write

    steps:
-    - uses: actions/checkout@v2
-    - name: Set up JDK 1.8
-      uses: actions/setup-java@v1
+    - uses: actions/checkout@v3
+    - name: Set up JDK 11
+      uses: actions/setup-java@v3
      with:
-        java-version: 1.8
+        java-version: '11'
+        distribution: 'temurin'
        server-id: github # Value of the distributionManagement/repository/id field of the pom.xml
        settings-path: ${{ github.workspace }} # location for the settings.xml file

@@ -27,4 +31,4 @@ jobs:
    - name: Publish to GitHub Packages Apache Maven
      run: mvn deploy -s $GITHUB_WORKSPACE/settings.xml
      env:
-        GITHUB_TOKEN: ${{ github.token }}
+        GITHUB_TOKEN: ${{ github.token }}
@@ -1,24 +0,0 @@
-# This workflow will build a Java project with Maven
-# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-maven
-
-name: Java CI with Maven
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up JDK 1.8
-      uses: actions/setup-java@v1
-      with:
-        java-version: 1.8
-    - name: Build with Maven
-      run: mvn -B package --file pom.xml
@@ -1,32 +0,0 @@
-name: MSBuild
-
-on: [push]
-
-env:
-  # Path to the solution file relative to the root of the project.
-  SOLUTION_FILE_PATH: .
-
-  # Configuration type to build.
-  # You can convert this to a build matrix if you need coverage of multiple configuration types.
-  # https://docs.github.com/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
-  BUILD_CONFIGURATION: Release
-
-jobs:
-  build:
-    runs-on: windows-latest
-
-    steps:
-    - uses: actions/checkout@v2
-
-    - name: Add MSBuild to PATH
-      uses: microsoft/setup-msbuild@v1
-
-    - name: Restore NuGet packages
-      working-directory: ${{env.GITHUB_WORKSPACE}}
-      run: nuget restore ${{env.SOLUTION_FILE_PATH}}
-
-    - name: Build
-      working-directory: ${{env.GITHUB_WORKSPACE}}
-      # Add additional options to the MSBuild command line here (like platform or verbosity level).
-      # See https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference
-      run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}
@@ -1,5 +1,5 @@
-# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
-# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs

 name: Node.js CI

@@ -16,15 +16,16 @@ jobs:

    strategy:
      matrix:
-        node-version: [10.x, 12.x, 14.x, 15.x]
+        node-version: [14.x, 16.x, 18.x]
        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
+      uses: actions/setup-node@v3
      with:
        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
    - run: npm ci
    - run: npm run build --if-present
    - run: npm test
@@ -0,0 +1,28 @@
+name: NodeJS with Grunt
+
+on:
+  push:
+    branches: [ $default-branch ]
+  pull_request:
+    branches: [ $default-branch ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [14.x, 16.x, 18.x]
+
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+
+    - name: Build
+      run: |
+        npm install
+        grunt
@@ -0,0 +1,28 @@
+name: NodeJS with Gulp
+
+on:
+  push:
+    branches: [ $default-branch ]
+  pull_request:
+    branches: [ $default-branch ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [14.x, 16.x, 18.x]
+
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+
+    - name: Build
+      run: |
+        npm install
+        gulp
@@ -0,0 +1,36 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - run: npm ci
+      - run: npm test
+
+  publish-gpr:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+          registry-url: $registry-url(npm)
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
@@ -1,5 +1,5 @@
 # This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
-# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages

 name: Node.js Package

@@ -11,10 +11,10 @@ jobs:
  build:
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v1
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
        with:
-          node-version: 12
+          node-version: 16
      - run: npm ci
      - run: npm test

@@ -22,26 +22,12 @@ jobs:
    needs: build
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v1
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
        with:
-          node-version: 12
+          node-version: 16
          registry-url: https://registry.npmjs.org/
      - run: npm ci
      - run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{secrets.npm_token}}
-
-  publish-gpr:
-    needs: build
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v1
-        with:
-          node-version: 12
-          registry-url: $registry-url(npm)
-      - run: npm ci
-      - run: npm publish
-        env:
-          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
@@ -0,0 +1,30 @@
+name: Xcode - Build and Analyze
+
+on:
+  push:
+    branches: [ $default-branch ]
+  pull_request:
+    branches: [ $default-branch ]
+
+jobs:
+  build:
+    name: Build and analyse default scheme using xcodebuild command
+    runs-on: macos-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Set Default Scheme
+        run: |
+          scheme_list=$(xcodebuild -list -json | tr -d "\n")
+          default=$(echo $scheme_list | ruby -e "require 'json'; puts JSON.parse(STDIN.gets)['project']['targets'][0]")
+          echo $default | cat >default
+          echo Using default scheme: $default
+      - name: Build
+        env:
+          scheme: ${{ 'default' }}
+        run: |
+          if [ $scheme = default ]; then scheme=$(cat default); fi
+          if [ "`ls -A | grep -i \\.xcworkspace\$`" ]; then filetype_parameter="workspace" && file_to_build="`ls -A | grep -i \\.xcworkspace\$`"; else filetype_parameter="project" && file_to_build="`ls -A | grep -i \\.xcodeproj\$`"; fi
+          file_to_build=`echo $file_to_build | awk '{$1=$1;print}'`
+          xcodebuild clean build analyze -scheme "$scheme" -"$filetype_parameter" "$file_to_build" | xcpretty && exit ${PIPESTATUS[0]}
@@ -1,152 +0,0 @@
-# This workflow uses actions that are not certified by GitHub.
-# They are provided by a third-party and are governed by
-# separate terms of service, privacy policy, and support
-# documentation.
-
-### The OpenShift Starter workflow will:
-# - Checkout your repository
-# - Perform a Docker build
-# - Push the built image to an image registry
-# - Log in to your OpenShift cluster
-# - Create an OpenShift app from the image and expose it to the internet.
-
-### Before you begin:
-# - Have write access to a container image registry such as quay.io or Dockerhub.
-# - Have access to an OpenShift cluster.
-#   - For instructions to get started with OpenShift see https://www.openshift.com/try
-# - The project you wish to add this workflow to should have a Dockerfile.
-#   - If you don't have a Dockerfile at the repository root, see the buildah-build step.
-#   - Builds from scratch are also available, but require more configuration.
-
-### To get the workflow running:
-# 1. Add this workflow to your repository.
-# 2. Edit the top-level 'env' section, which contains a list of environment variables that must be configured.
-# 3. Create the secrets referenced in the 'env' section under your repository Settings.
-# 4. Edit the 'branches' in the 'on' section to trigger the workflow on a push to your branch.
-# 5. Commit and push your changes.
-
-# For a more sophisticated example, see https://github.com/redhat-actions/spring-petclinic/blob/main/.github/workflows/petclinic-sample.yaml
-# Also see our GitHub organization, https://github.com/redhat-actions/
-
-name: OpenShift
-
-# ⬇️  Modify the fields marked with ⬇️ to fit your project, and create any secrets that are referenced.
-# https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets
-env:
-  # ⬇️ EDIT with your registry and registry path.
-  REGISTRY: quay.io/<username>
-  # ⬇️ EDIT with your registry username.
-  REGISTRY_USER: <username>
-  REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
-
-  # ⬇️ EDIT to log into your OpenShift cluster and set up the context.
-  # See https://github.com/redhat-actions/oc-login#readme for how to retrieve these values.
-  OPENSHIFT_SERVER: ${{ secrets.OPENSHIFT_SERVER }}
-  OPENSHIFT_TOKEN: ${{ secrets.OPENSHIFT_TOKEN }}
-
-  # ⬇️ EDIT with the port your application should be accessible on.
-  APP_PORT: 8080
-
-  # ⬇️ EDIT if you wish to set the kube context's namespace after login. Leave blank to use the default namespace.
-  OPENSHIFT_NAMESPACE: ""
-
-  # If you wish to manually provide the APP_NAME and TAG, set them here, otherwise they will be auto-detected.
-  APP_NAME: ""
-  TAG: ""
-
-on:
-  # https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows
-  push:
-    # Edit to the branch(es) you want to build and deploy on each push.
-    branches: [ $default-branch ]
-
-jobs:
-  openshift-ci-cd:
-    name: Build and deploy to OpenShift
-    runs-on: ubuntu-20.04
-
-    steps:
-    - uses: actions/checkout@v2
-
-    - name: Determine app name
-      if: env.APP_NAME == ''
-      run: |
-        echo "APP_NAME=$(basename $PWD)" | tee -a $GITHUB_ENV
-
-    - name: Determine tag
-      if: env.TAG == ''
-      run: |
-        echo "TAG=${GITHUB_SHA::7}" | tee -a $GITHUB_ENV
-
-    # https://github.com/redhat-actions/buildah-build#readme
-    - name: Build from Dockerfile
-      uses: redhat-actions/buildah-build@v1
-      with:
-        image: ${{ env.APP_NAME }}
-        tag: ${{ env.TAG }}
-        # If you don't have a dockerfile, see:
-        # https://github.com/redhat-actions/buildah-build#building-from-scratch
-        # Otherwise, point this to your Dockerfile relative to the repository root.
-        dockerfiles: |
-          ./Dockerfile
-
-    # https://github.com/redhat-actions/push-to-registry#readme
-    - name: Push to registry
-      id: push-to-registry
-      uses: redhat-actions/push-to-registry@v1
-      with:
-        image: ${{ env.APP_NAME }}
-        tag: ${{ env.TAG }}
-        registry: ${{ env.REGISTRY }}
-        username: ${{ env.REGISTRY_USER }}
-        password: ${{ env.REGISTRY_PASSWORD }}
-
-    # The path the image was pushed to is now stored in ${{ steps.push-to-registry.outputs.registry-path }}
-
-    # oc-login works on all platforms, but oc must be installed first.
-    # The GitHub Ubuntu runner already includes oc.
-    # Otherwise, https://github.com/redhat-actions/oc-installer#readme is available.
-
-    # https://github.com/redhat-actions/oc-login#readme
-    - name: Log in to OpenShift
-      uses: redhat-actions/oc-login@v1
-      with:
-        openshift_server_url: ${{ env.OPENSHIFT_SERVER }}
-        openshift_token: ${{ env.OPENSHIFT_TOKEN }}
-        insecure_skip_tls_verify: true
-        namespace: ${{ env.OPENSHIFT_NAMESPACE }}
-
-    # This step should create a deployment, service, and route to run your app and expose it to the internet.
-    # Feel free to replace this with 'oc apply', 'helm install', or however you like to deploy your app.
-    - name: Create and expose app
-      run: |
-        export IMAGE="${{ steps.push-to-registry.outputs.registry-path }}"
-        export PORT=${{ env.APP_PORT }}
-
-        export SELECTOR="app=${{ env.APP_NAME }}"
-        echo "SELECTOR=$SELECTOR" >> $GITHUB_ENV
-
-        set -x
-        # Take down any old deployment
-        oc delete all --selector="$SELECTOR"
-        oc new-app --name $APP_NAME --docker-image="$IMAGE"
-
-        # Make sure the app port is exposed
-        oc patch svc $APP_NAME -p "{ \"spec\": { \"ports\": [{ \"name\": \"$PORT-tcp\", \"port\": $PORT }] } }"
-        oc expose service $APP_NAME --port=$PORT
-
-        oc get all --selector="$SELECTOR"
-        set +x
-
-        export ROUTE="$(oc get route $APP_NAME -o jsonpath='{.spec.host}')"
-        echo "$APP_NAME is exposed at $ROUTE"
-        echo "ROUTE=$ROUTE" >> $GITHUB_ENV
-
-    - name: View application route
-      run: |
-        [[ -n ${{ env.ROUTE }} ]] || (echo "Determining application route failed in previous step"; exit 1)
-        echo "======================== Your application is available at: ========================"
-        echo ${{ env.ROUTE }}
-        echo "==================================================================================="
-        echo
-        echo "Your app can be taken down with: \"oc delete all --selector='${{ env.SELECTOR }}'\""
@@ -6,20 +6,23 @@ on:
  pull_request:
    branches: [ $default-branch ]

+permissions:
+  contents: read
+
 jobs:
  build:

    runs-on: ubuntu-latest

    steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3

    - name: Validate composer.json and composer.lock
-      run: composer validate
+      run: composer validate --strict

    - name: Cache Composer packages
      id: composer-cache
-      uses: actions/cache@v2
+      uses: actions/cache@v3
      with:
        path: vendor
        key: ${{ runner.os }}-php-${{ hashFiles('**/composer.lock') }}
@@ -27,8 +30,7 @@ jobs:
          ${{ runner.os }}-php-

    - name: Install dependencies
-      if: steps.composer-cache.outputs.cache-hit != 'true'
-      run: composer install --prefer-dist --no-progress --no-suggest
+      run: composer install --prefer-dist --no-progress

    # Add a test script to composer.json, for instance: "test": "vendor/bin/phpunit"
    # Docs: https://getcomposer.org/doc/articles/scripts.md
@@ -2,5 +2,5 @@
    "name": "Ada",
    "description": "Build Ada project with GPRbuild.",
    "iconName": "ada",
-    "categories": ["Ada"]
+    "categories": ["Continuous integration", "Ada"]
 }
@@ -1,7 +0,0 @@
-{
-    "name": "Deploy to Alibaba Cloud ACK",
-    "description": "Deploy a container to Alibaba Cloud Container Service for Kubernetes (ACK).",
-    "creator": "Alibaba Cloud",
-    "iconName": "alibabacloud",
-    "categories": null
-}
@@ -2,5 +2,5 @@
    "name": "Android CI",
    "description": "Build an Android project with Gradle.",
    "iconName": "android",
-    "categories": ["Java", "Mobile"]
+    "categories": ["Continuous integration", "Java", "Mobile"]
 }
@@ -2,5 +2,5 @@
    "name": "Java with Ant",
    "description": "Build and test a Java project with Apache Ant.",
    "iconName": "ant",
-    "categories": ["Ant", "Java"]
+    "categories": ["Continuous integration", "Ant", "Java"]
 }
@@ -1,7 +0,0 @@
-{
-    "name": "Deploy to Amazon ECS",
-    "description": "Deploy a container to an Amazon ECS service powered by AWS Fargate or Amazon EC2.",
-    "creator": "Amazon Web Services",
-    "iconName": "aws",
-    "categories": null
-}
@@ -1,7 +0,0 @@
-{
-    "name": "Deploy Node.js to Azure Web App",
-    "description": "Build a Node.js project and deploy it to an Azure Web App.",
-    "creator": "Microsoft Azure",
-    "iconName": "azure",
-    "categories": null
-}
@@ -1,6 +1,7 @@
 {
    "name": "Simple workflow",
    "description": "Start with a file with the minimum necessary structure.",
+    "creator": "GitHub",
    "iconName": "blank",
    "categories": null
 }
@@ -2,5 +2,5 @@
    "name": "C/C++ with Make",
    "description": "Build and test a C/C++ project using Make.",
    "iconName": "c-cpp",
-    "categories": ["C", "C++"]
+    "categories": ["Continuous integration", "C", "C++"]
 }
@@ -2,5 +2,5 @@
    "name": "Clojure",
    "description": "Build and test a Clojure project with Leiningen.",
    "iconName": "clojure",
-    "categories": ["Clojure", "Java"]
+    "categories": ["Continuous integration", "Clojure", "Java"]
 }
@@ -0,0 +1,6 @@
+{
+    "name": "CMake based, multi-platform projects",
+    "description": "Build and test a CMake based project on multiple platforms.",
+    "iconName": "cmake",
+    "categories": ["Continuous integration", "C", "C++"]
+}
@@ -0,0 +1,6 @@
+{
+    "name": "CMake based, single-platform projects",
+    "description": "Build and test a CMake based project on a single-platform.",
+    "iconName": "cmake",
+    "categories": ["Continuous integration", "C", "C++"]
+}
@@ -1,6 +0,0 @@
-{
-    "name": "CMake based projects",
-    "description": "Build and test a CMake based project.",
-    "iconName": "cmake",
-    "categories": ["C", "C++"]
-}
@@ -2,5 +2,5 @@
    "name": "Crystal",
    "description": "Build and test a Crystal project.",
    "iconName": "crystal",
-    "categories": ["Crystal"]
+    "categories": ["Continuous integration", "Crystal"]
 }
@@ -1,6 +0,0 @@
-{
-    "name": "D",
-    "description": "Build and test a D project with dub.",
-    "iconName": "d",
-    "categories": [ "D" ]
-}
@@ -1,6 +0,0 @@
-{
-    "name": "Dart",
-    "description": "Build and test a Dart project with Pub.",
-    "iconName": "dart",
-    "categories": ["Dart"]
-}
@@ -1,6 +0,0 @@
-{
-    "name": "Deno",
-    "description": "Test your Deno project",
-    "iconName": "deno",
-    "categories": ["JavaScript", "TypeScript", "Deno"]
-}
@@ -2,5 +2,5 @@
    "name": "Django",
    "description": "Build and Test a Django Project",
    "iconName": "django",
-    "categories": ["Python", "Django"]
+    "categories": ["Continuous integration", "Python", "Django"]
 }
@@ -2,5 +2,5 @@
    "name": "Docker image",
    "description": "Build a Docker image to deploy, run, or push to a registry.",
    "iconName": "docker",
-    "categories": ["Dockerfile"]
+    "categories": ["Continuous integration", "Dockerfile"]
 }
@@ -1,6 +0,0 @@
-{
-  "name": "Publish Docker Container",
-  "description": "Build, test and push Docker image to GitHub Packages.",
-  "iconName": "docker",
-  "categories": ["Dockerfile"]
-}
@@ -1,6 +0,0 @@
-{
-    "name": ".NET Desktop",
-    "description": "Build, test, sign and publish a desktop application built on .NET.",
-    "iconName": "dotnet",
-    "categories": ["C#", "Visual Basic", "WPF", ".NET"]
-}
@@ -2,5 +2,5 @@
    "name": ".NET",
    "description": "Build and test a .NET or ASP.NET Core project.",
    "iconName": "dotnet",
-    "categories": ["C#", "F#", "Visual Basic", "ASP", "ASP.NET", ".NET"]
+    "categories": ["Continuous integration", "C#", "F#", "Visual Basic", "ASP", "ASP.NET", ".NET", "AspNetCore", "DotNetConsole"]
 }
@@ -1,6 +0,0 @@
-{
-    "name": "Elixir",
-    "description": "Build and test an Elixir project with Mix.",
-    "iconName": "elixir",
-    "categories": ["Elixir", "Erlang"]
-}
@@ -2,5 +2,5 @@
    "name": "Erlang",
    "description": "Build and test an Erlang project with rebar.",
    "iconName": "erlang",
-    "categories": ["Erlang"]
+    "categories": ["Continuous integration", "Erlang"]
 }
@@ -1,6 +0,0 @@
-{
-    "name": "Ruby Gem",
-    "description": "Pushes a Ruby Gem to RubyGems and GitHub Package Registry.",
-    "iconName": "ruby-gems",
-    "categories": ["Ruby", "SDLC"]
-}
@@ -0,0 +1,7 @@
+{
+    "name": "SLSA Generic generator",
+    "creator": "Open Source Security Foundation (OpenSSF)",
+    "description": "Generate SLSA3 provenance for your existing release workflows",
+    "iconName": "generator-generic-ossf-slsa3-publish",
+    "categories": ["Continuous integration", "Go", "Elixir", "Erlang", "PHP", "Haskell", "Rust", "Java", "Scala", "Gradle", "Maven", "Python", "C", "C++", "TypeScript", "JavaScript", "npm", "Ruby", "HTML", "Composer", "Makefile", "Ada"]
+}
@@ -0,0 +1,7 @@
+{
+    "name": "SLSA Go releaser",
+    "creator": "Open Source Security Foundation (OpenSSF)",
+    "description": "Compile your Go project using a SLSA3 compliant builder",
+    "iconName": "go-ossf-slsa3-publish",
+    "categories": ["Continuous integration", "Go"]
+}
@@ -2,5 +2,5 @@
    "name": "Go",
    "description": "Build a Go project.",
    "iconName": "go",
-    "categories": ["Go"]
+    "categories": ["Continuous integration", "Go"]
 }
@@ -1,7 +0,0 @@
-{
-    "name": "Build and Deploy to GKE",
-    "description": "Build a docker container, publish it to Google Container Registry, and deploy to GKE.",
-    "creator": "Google Cloud",
-    "iconName": "googlegke",
-    "categories": null
-}
@@ -1,6 +0,0 @@
-{
-    "name": "Publish Java Package with Gradle",
-    "description": "Build a Java Package using Gradle and publish to GitHub Packages.",
-    "iconName": "gradle",
-    "categories": ["Java", "Gradle"]
-}
@@ -1,6 +0,0 @@
-{
-    "name": "Java with Gradle",
-    "description": "Build and test a Java project using a Gradle wrapper script.",
-    "iconName": "gradle",
-    "categories": ["Java", "Gradle"]
-}
@@ -1,6 +0,0 @@
-{
-    "name": "Haskell",
-    "description": "Build and test a Haskell project with Cabal.",
-    "iconName": "haskell",
-    "categories": ["Haskell"]
-}
@@ -1,7 +0,0 @@
-{
-    "name": "Deploy to IBM Cloud Kubernetes Service",
-    "description": "Build a docker container, publish it to IBM Cloud Container Registry, and deploy to IBM Cloud Kubernetes Service.",
-    "creator": "IBM",
-    "iconName": "ibm",
-    "categories": null
-}
@@ -3,6 +3,7 @@
    "description": "Build and test an iOS application using xcodebuild and any available iPhone simulator.",
    "iconName": "xcode",
    "categories": [
+        "Continuous integration",
        "iOS",
        "Xcode"
    ]
@@ -1,6 +1,6 @@
 {
-    "name": "Jekyll",
+    "name": "Jekyll using Docker image",
    "description": "Package a Jekyll site using the jekyll/builder Docker image.",
    "iconName": "jekyll",
-    "categories": ["HTML"]
+    "categories": ["Continuous integration", "HTML"]
 }
@@ -1,9 +0,0 @@
-{
-    "name": "Laravel",
-    "description": "Test a Laravel project.",
-    "iconName": "php",
-    "categories": [
-        "PHP",
-        "Laravel"
-    ]
-}
@@ -0,0 +1,6 @@
+{
+    "name": "Build projects with Make",
+    "description": "Build and test a project using Make.",
+    "iconName": "makefile",
+    "categories": ["Continuous integration", "Makefile"]
+}
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
GitHub Actions	60cf90b26e	Updating GHES workflows	2024-04-18 19:39:37 +00:00
Fabian Aguilar Gomez	43ab435b51	Merge pull request #2366 from actions/pages-ghes-3.13 Revert Pages actions to last ones compatible with GHES	2024-04-17 17:47:01 -05:00
GitHub Actions	b2e9b953bf	Updating GHES workflows	2024-04-11 11:17:41 +00:00
Yoann Chaudet	0329dc03ce	Revert Pages actions to last ones compatible with GHES	2024-04-05 14:22:52 -07:00
GitHub Actions	8d2a913ae0	Updating GHES workflows	2024-04-03 15:22:51 +00:00
GitHub Actions	8c7ee816e0	Updating GHES workflows	2024-03-30 01:21:25 +00:00
GitHub Actions	17fe5c7de8	Updating GHES workflows	2024-03-30 01:10:11 +00:00
GitHub Actions	9eade7871e	Updating GHES workflows	2024-03-28 03:40:28 +00:00
GitHub Actions	5b42f56a6a	Updating GHES workflows	2024-03-27 17:52:17 +00:00
GitHub Actions	d5665549c5	Updating GHES workflows	2024-03-26 13:13:29 +00:00
GitHub Actions	3f976c4682	Updating GHES workflows	2024-03-25 23:27:10 +00:00
GitHub Actions	1321cdf994	Updating GHES workflows	2024-03-12 19:08:45 +00:00
GitHub Actions	5b1bc4080e	Updating GHES workflows	2024-01-29 20:29:26 +00:00
GitHub Actions	6c250eb62e	Updating GHES workflows	2024-01-10 22:12:47 +00:00
GitHub Actions	1a4b2218a8	Updating GHES workflows	2023-12-22 19:39:02 +00:00
GitHub Actions	f5e9c68376	Updating GHES workflows	2023-12-14 13:02:11 +00:00
GitHub Actions	4e54349850	Updating GHES workflows	2023-12-04 21:54:19 +00:00
GitHub Actions	fc1b4b5a61	Updating GHES workflows	2023-12-04 11:03:32 +00:00
GitHub Actions	0059fec5f8	Updating GHES workflows	2023-10-03 07:58:37 +00:00
GitHub Actions	bcdba11782	Updating GHES workflows	2023-08-11 00:05:55 +00:00
GitHub Actions	e529eb20ed	Updating GHES workflows	2023-07-13 15:47:27 +00:00
GitHub Actions	7453014501	Updating GHES workflows	2023-07-13 14:42:30 +00:00
GitHub Actions	9f31adb6cc	Updating GHES workflows	2023-07-13 14:40:36 +00:00
GitHub Actions	c34a432b17	Updating GHES workflows	2023-07-13 14:11:22 +00:00
GitHub Actions	82719ed8ae	Updating GHES workflows	2023-07-12 16:40:18 +00:00
GitHub Actions	7942bd898b	Updating GHES workflows	2023-06-13 18:05:57 +00:00
GitHub Actions	91bc191de0	Updating GHES workflows	2023-06-02 08:51:39 +00:00
GitHub Actions	22f025c6ab	Updating GHES workflows	2023-05-31 19:17:44 +00:00
GitHub Actions	d85ab73e08	Updating GHES workflows	2023-04-18 18:45:37 +00:00
GitHub Actions	3f16403080	Updating GHES workflows	2023-04-18 16:22:05 +00:00
GitHub Actions	1002117c0c	Updating GHES workflows	2023-03-27 22:19:59 +00:00
GitHub Actions	8db6f2a36e	Updating GHES workflows	2023-03-27 22:15:55 +00:00
GitHub Actions	c61a258aad	Updating GHES workflows	2023-03-14 16:06:49 +00:00
GitHub Actions	661eb08820	Updating GHES workflows	2023-03-14 16:06:02 +00:00
GitHub Actions	21cc118c35	Updating GHES workflows	2023-03-14 05:26:45 +00:00
GitHub Actions	f64df68890	Updating GHES workflows	2023-03-10 12:38:21 +00:00
GitHub Actions	b35bf7d6f6	Updating GHES workflows	2023-03-10 00:58:03 +00:00
GitHub Actions	b2167d7786	Updating GHES workflows	2023-03-09 19:11:51 +00:00
GitHub Actions	14591aecf7	Updating GHES workflows	2023-03-09 17:55:38 +00:00
GitHub Actions	e1cecc376a	Updating GHES workflows	2023-01-26 00:44:29 +00:00
GitHub Actions	0e88c801eb	Updating GHES workflows	2023-01-23 17:32:59 +00:00
GitHub Actions	9124a2783a	Updating GHES workflows	2023-01-03 08:18:57 +00:00
GitHub Actions	443384d635	Updating GHES workflows	2023-01-03 08:12:59 +00:00
GitHub Actions	1acff35e6b	Updating GHES workflows	2022-12-14 21:06:03 +00:00
GitHub Actions	7eefe684f7	Updating GHES workflows	2022-12-14 13:39:33 +00:00
GitHub Actions	97a60b2516	Updating GHES workflows	2022-12-13 12:32:36 +00:00
GitHub Actions	8ca82d473a	Updating GHES workflows	2022-12-13 10:42:26 +00:00
GitHub Actions	c7deaaa7a7	Updating GHES workflows	2022-12-08 06:04:15 +00:00
GitHub Actions	dd6165f804	Updating GHES workflows	2022-11-23 19:25:09 +00:00
GitHub Actions	56cd01b1bb	Updating GHES workflows	2022-11-23 15:22:50 +00:00
GitHub Actions	a8f630895c	Updating GHES workflows	2022-11-22 21:06:04 +00:00
GitHub Actions	f9115b3429	Updating GHES workflows	2022-11-22 21:04:49 +00:00
GitHub Actions	08abd1ed14	Updating GHES workflows	2022-11-10 13:45:36 +00:00
GitHub Actions	92e51bbc9a	Updating GHES workflows	2022-10-28 10:35:26 +00:00
GitHub Actions	a55693d47e	Updating GHES workflows	2022-10-27 18:15:30 +00:00
GitHub Actions	62588429e6	Updating GHES workflows	2022-10-27 07:05:03 +00:00
GitHub Actions	e19b783da4	Updating GHES workflows	2022-10-25 11:07:58 +00:00
GitHub Actions	623da53b9d	Updating GHES workflows	2022-10-20 04:29:35 +00:00
GitHub Actions	c757f4d1a1	Updating GHES workflows	2022-10-13 05:35:30 +00:00
GitHub Actions	51d26076d6	Updating GHES workflows	2022-09-30 12:21:47 +00:00
GitHub Actions	7f1d660112	Updating GHES workflows	2022-09-22 11:46:26 +00:00
GitHub Actions	9038abce30	Updating GHES workflows	2022-09-21 15:06:01 +00:00
GitHub Actions	ce61da64bd	Updating GHES workflows	2022-09-14 10:57:16 +00:00
GitHub Actions	62e7cb9cae	Updating GHES workflows	2022-09-14 06:52:18 +00:00
GitHub Actions	d82f976075	Updating GHES workflows	2022-09-14 06:43:11 +00:00
GitHub Actions	e7fc998ec0	Updating GHES workflows	2022-09-14 06:18:41 +00:00
Mingzi	7cae5f2c7b	Merge pull request #1731 from actions/add-pages-icons backfill pages icon to ghes branch	2022-09-07 12:13:29 -07:00
yimysty	cf827c2500	backfill pages icon to ghes branch	2022-09-07 12:12:16 -07:00
Jess Bees	20fa1bb179	Merge pull request #1710 from actions/starter-workflows-on-ghes Apply pages workflow updates to ghes	2022-08-29 16:38:10 -04:00
James M. Greene	3c6ad93f44	Add optional quotes to Hugo CLI baseURL	2022-08-26 08:39:10 -04:00
James M. Greene	fff5dd325b	Clarify './_site' directory usage	2022-08-26 08:39:10 -04:00
James M. Greene	564a986028	Remove unused step ID from a few Pages workflows	2022-08-26 08:39:10 -04:00
James M. Greene	0c73cd6a36	Add a trailing slash back into the Hugo starter workflow for maximum backward compatibility with themes	2022-08-26 08:37:15 -04:00
James M. Greene	79875644f2	Update Pages starter workflows to use actions/configure-pages@v2	2022-08-26 08:37:15 -04:00
GitHub Actions	10d60db629	Updating GHES workflows	2022-08-26 04:29:52 +00:00
Jess Bees	42c2f16aaa	Merge pull request #1698 from actions/pages-workflows-on-ghes Add pages workflows	2022-08-24 15:19:25 -04:00
Jess Bees	876c20705a	Add pages workflows	2022-08-24 14:52:59 -04:00
GitHub Actions	8f1e64a8a6	Updating GHES workflows	2022-07-20 11:47:44 +00:00
GitHub Actions	50fbfabb49	Updating GHES workflows	2022-07-18 12:25:02 +00:00
GitHub Actions	52389f7770	Updating GHES workflows	2022-06-22 11:45:41 +00:00
GitHub Actions	f8680514c7	Updating GHES workflows	2022-06-21 08:42:31 +00:00
GitHub Actions	692f5f05ad	Updating GHES workflows	2022-06-20 06:24:55 +00:00
GitHub Actions	f5b98487a3	Updating GHES workflows	2022-05-04 05:52:48 +00:00
GitHub Actions	6a203a9f51	Updating GHES workflows	2022-04-26 18:52:33 +00:00
GitHub Actions	3b01a31221	Updating GHES workflows	2022-04-14 06:05:23 +00:00
GitHub Actions	0763e02a9d	Updating GHES workflows	2022-04-13 05:54:18 +00:00
GitHub Actions	e151dba495	Updating GHES workflows	2022-04-10 19:47:24 +00:00
GitHub Actions	0eadf71408	Updating GHES workflows	2022-03-31 13:39:38 +00:00
GitHub Actions	51a372807b	Updating GHES workflows	2022-03-30 09:50:11 +00:00
GitHub Actions	3cd1bccb03	Updating GHES workflows	2022-03-30 09:22:31 +00:00
GitHub Actions	1cddd5754c	Updating GHES workflows	2022-03-28 17:11:12 +00:00
GitHub Actions	2fe221019a	Updating GHES workflows	2022-02-11 17:02:43 +00:00
GitHub Actions	f982942d7a	Updating GHES workflows	2022-01-27 04:59:07 +00:00
GitHub Actions	5625253e4f	Updating GHES workflows	2022-01-27 04:57:54 +00:00
GitHub Actions	22ab3ffdb2	Updating GHES workflows	2022-01-20 03:31:26 +00:00
GitHub Actions	b9d98964bb	Updating GHES workflows	2022-01-14 23:06:01 +00:00
GitHub Actions	726a1fde56	Updating GHES workflows	2021-12-02 22:23:16 +00:00
GitHub Actions	f0ae974e62	Updating GHES workflows	2021-12-02 03:51:52 +00:00
GitHub Actions	e56f0a3e95	Updating GHES workflows	2021-12-01 19:39:01 +00:00
GitHub Actions	337d7a06ff	Updating GHES workflows	2021-11-25 10:15:57 +00:00
GitHub Actions	f01e7eb9b0	Updating GHES workflows	2021-10-27 14:08:44 +00:00
GitHub Actions	345e123521	Updating GHES workflows	2021-09-23 05:00:12 +00:00
GitHub Actions	1d2cedfc3f	Updating GHES workflows	2021-09-21 08:05:52 +00:00
GitHub Actions	8be9ca9951	Updating GHES workflows	2021-09-16 06:22:17 +00:00
GitHub Actions	2433143cca	Updating GHES workflows	2021-09-16 05:49:38 +00:00
GitHub Actions	4f21509afc	Updating GHES workflows	2021-09-16 05:48:19 +00:00
GitHub Actions	3623a790cb	Updating GHES workflows	2021-09-16 05:32:44 +00:00
GitHub Actions	32719e08a6	Updating GHES workflows	2021-09-16 05:30:31 +00:00
GitHub Actions	3613922186	Updating GHES workflows	2021-09-14 02:35:24 +00:00
GitHub Actions	c872171c0c	Updating GHES workflows	2021-09-09 10:47:00 +00:00
GitHub Actions	a5d8a24850	Updating GHES workflows	2021-09-08 10:05:32 +00:00
GitHub Actions	c6a566944c	Updating GHES workflows	2021-09-01 18:54:06 +00:00
GitHub Actions	7529a578eb	Updating GHES workflows	2021-08-25 04:29:16 +00:00
GitHub Actions	6db2679ba5	Updating GHES workflows	2021-08-24 15:28:18 +00:00
GitHub Actions	6cdaf1fd48	Updating GHES workflows	2021-08-18 23:28:41 +00:00
GitHub Actions	49dc04ba87	Updating GHES workflows	2021-07-26 15:27:09 +00:00
GitHub Actions	64a66cc158	Updating GHES workflows	2021-07-26 11:15:04 +00:00
GitHub Actions	920b11c2f0	Updating GHES workflows	2021-07-01 12:58:50 +00:00
GitHub Actions	09d65e8bb9	Updating GHES workflows	2021-06-25 21:00:29 +00:00
GitHub Actions	fc6320d8d1	Updating GHES workflows	2021-06-25 20:57:32 +00:00
GitHub Actions	c8e5f9fd1c	Updating GHES workflows	2021-06-23 19:16:16 +00:00
GitHub Actions	96094e8e76	Updating GHES workflows	2021-06-21 17:56:28 +00:00
GitHub Actions	050f2780b3	Updating GHES workflows	2021-06-16 02:09:59 +00:00
GitHub Actions	67c938b27c	Updating GHES workflows	2021-06-14 17:29:19 +00:00
GitHub Actions	0c0632eda0	Updating GHES workflows	2021-06-03 19:07:39 +00:00
GitHub Actions	e0ca396890	Updating GHES workflows	2021-06-02 23:04:58 +00:00
GitHub Actions	9858eebcaa	Updating GHES workflows	2021-05-05 15:46:33 +00:00
GitHub Actions	4fc6cb167f	Updating GHES workflows	2021-04-27 18:38:04 +00:00
GitHub Actions	5de4fccfd1	Updating GHES workflows	2021-04-27 15:14:34 +00:00
GitHub Actions	bb7e655faa	Updating GHES workflows	2021-04-16 21:28:56 +00:00
GitHub Actions	4ec495b664	Updating GHES workflows	2021-04-09 22:34:42 +00:00
GitHub Actions	e2eeba9fc2	Updating GHES workflows	2021-04-05 15:31:49 +00:00
GitHub Actions	b35c8db5d7	Updating GHES workflows	2021-02-26 22:25:50 +00:00
GitHub Actions	17479bc603	Updating GHES workflows	2021-01-15 20:21:19 +00:00
GitHub Actions	3c3f778c30	Updating GHES workflows	2021-01-05 16:48:50 +00:00
GitHub Actions	0c8aae959b	Updating GHES workflows	2021-01-04 18:52:55 +00:00
GitHub Actions	29002989f9	Updating GHES workflows	2021-01-04 16:17:06 +00:00
GitHub Actions	c21d165d2c	Updating GHES workflows	2020-12-18 20:58:48 +00:00
GitHub Actions	dab11a230a	Updating GHES workflows	2020-12-18 20:01:57 +00:00
GitHub Actions	f51edc98f2	Updating GHES workflows	2020-12-15 01:08:26 +00:00
GitHub Actions	2943b3eb50	Updating GHES workflows	2020-12-07 18:16:29 +00:00
GitHub Actions	0b4494c105	Updating GHES workflows	2020-11-30 17:02:58 +00:00
GitHub Actions	3860b7d860	Updating GHES workflows	2020-11-25 21:02:59 +00:00
GitHub Actions	263c7fa53e	Updating GHES workflows	2020-11-25 18:16:14 +00:00
GitHub Actions	efc30081fa	Updating GHES workflows	2020-11-24 21:43:18 +00:00
GitHub Actions	c89663c3cf	Updating GHES workflows	2020-11-24 21:22:16 +00:00
GitHub Actions	ebc9aa330a	Updating GHES workflows	2020-11-19 22:27:39 +00:00
GitHub Actions	7fd11cddc6	Updating GHES workflows	2020-11-09 20:32:31 +00:00
GitHub Actions	9a682491ac	Updating GHES workflows	2020-11-06 18:26:42 +00:00
GitHub Actions	cb8bb12037	Updating GHES workflows	2020-10-21 20:29:07 +00:00
GitHub Actions	2d913365dc	Updating GHES workflows	2020-10-21 20:25:45 +00:00
GitHub Actions	d30f415002	Updating GHES workflows	2020-10-14 15:02:53 +00:00
GitHub Actions	2de65d448a	Updating GHES workflows	2020-09-28 22:04:42 +00:00
GitHub Actions	e63b3cb8d3	Updating GHES workflows	2020-09-10 00:21:31 +00:00
GitHub Actions	a618a4364d	Updating GHES workflows	2020-09-03 23:25:00 +00:00
GitHub Actions	9d5f3ec540	Updating GHES workflows	2020-09-01 16:43:53 +00:00
GitHub Actions	5e628d6090	Updating GHES workflows	2020-08-26 22:06:09 +00:00
GitHub Actions	10105b6aa9	Updating GHES workflows	2020-08-25 16:17:33 +00:00
GitHub Actions	904fe4006e	Updating GHES workflows	2020-08-24 16:58:48 +00:00
GitHub Actions	1612e273ef	Updating GHES workflows	2020-08-24 16:57:10 +00:00
GitHub Actions	fc246debda	Updating GHES workflows	2020-08-21 18:57:48 +00:00
GitHub Actions	3869d8c7da	Updating GHES workflows	2020-08-21 15:27:57 +00:00
GitHub Actions	2e806ae206	Updating GHES workflows	2020-07-22 13:44:30 +00:00
GitHub Actions	0287d66cf4	Updating GHES workflows	2020-07-20 15:14:33 +00:00
GitHub Actions	934f35df00	Updating GHES workflows	2020-07-20 15:13:41 +00:00
GitHub Actions	def70d7268	Updating GHES workflows	2020-07-14 18:11:40 +00:00
GitHub Actions	a793bf3bd4	Updating GHES workflows	2020-07-09 18:07:41 +00:00
GitHub Actions	ddfbfeaade	Updating GHES workflows	2020-06-08 15:35:29 +00:00
GitHub Actions	1ff7963a8f	Updating GHES workflows	2020-05-27 14:59:35 +00:00
GitHub Actions	85199a93ce	Updating GHES workflows	2020-05-25 20:17:18 +00:00
GitHub Actions	874062869c	Updating GHES workflows	2020-05-25 20:13:54 +00:00
GitHub Actions	7f38c08e7a	Updating GHES workflows	2020-05-25 19:49:26 +00:00
GitHub Actions	07ab99db5c	Updating GHES workflows	2020-05-22 15:44:59 +00:00
GitHub Actions	2ba37119d3	Updating GHES workflows	2020-05-20 18:39:56 +00:00