Remove properties.

.github/labeler.yml

@@ -1,3 +0,0 @@
-# Add 'code-scanning' label to any changes within 'code-scanning' folder or any subfolders
-code-scanning:
-- code-scanning/**/*

.github/pull_request_template.md

@@ -1,60 +1,31 @@
-<!--
-IMPORTANT:
+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:
 
-This repository contains configuration for what users see when they click on the `Actions` tab and the setup page for Code Scanning.
+- [ ] Include a good description of the workflow.
+- [ ] Links to the language or tool will be nice (unless its really obvious)
 
-It is not:
-* A playground to try out scripts
-* A place for you to create a workflow for your repository
--->
+In the workflow and properties files:
 
-## Pre-requisites
+- [ ] The workflow filename of CI workflows should be the name of the language or platform, in lower case.  Special characters should be removed or replaced with words as appropriate (for example, "dotnet" instead of ".NET").
 
-- [ ] Prior to submitting a new workflow, please apply to join the GitHub Technology Partner Program: [partner.github.com/apply](https://partner.github.com/apply?partnershipType=Technology+Partner).
+  The workflow filename of publishing workflows should be the name of the language or platform, in lower case, followed by "-publish".
+- [ ] Includes a matching `ci/properties/*.properties.json` file.
+- [ ] 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: [ master ]` and `pull_request` to `branches: [ master ]`.
 
----
+  Packaging workflows should run on `release` with `types: [ created ]`.
 
-### **Please note that at this time we are only accepting new starter workflows for Code Scanning. Updates to existing starter workflows are fine.**
+Some general notes:
 
----
+- [ ] This workflow must only use actions that are produced by GitHub, [in the `actions` organization](https://github.com/actions), **or**
 
-## Tasks
-
-**For _all_ workflows, the workflow:**
-
-- [ ] Should be contained in a `.yml` file with the language or platform as its filename, in lower, [_kebab-cased_](https://en.wikipedia.org/wiki/Kebab_case) format (for example, [`docker-image.yml`](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml)).  Special characters should be removed or replaced with words as appropriate (for example, "dotnet" instead of ".NET").
-- [ ] Should use sentence case for the names of workflows and steps (for example, "Run tests").
-- [ ] Should be named _only_ by the name of the language or platform (for example, "Go", not "Go CI" or "Go Build").
-- [ ] Should include comments in the workflow for any parts that are not obvious or could use clarification.
-
-**For _CI_ workflows, the workflow:**
-
-- [ ] Should be preserved under [the `ci` directory](https://github.com/actions/starter-workflows/tree/main/ci).
-- [ ] Should include a matching `ci/properties/*.properties.json` file (for example, [`ci/properties/docker-publish.properties.json`](https://github.com/actions/starter-workflows/blob/main/ci/properties/docker-publish.properties.json)).
-- [ ] Should run on `push` to `branches: [ $default-branch ]` and `pull_request` to `branches: [ $default-branch ]`.
-- [ ] Packaging workflows should run on `release` with `types: [ created ]`.
-- [ ] Publishing workflows should have a filename that is the name of the language or platform, in lower case, followed by "-publish" (for example, [`docker-publish.yml`](https://github.com/actions/starter-workflows/blob/main/ci/docker-publish.yml)).
-
-**For _Code Scanning_ workflows, the workflow:**
-
-- [ ] Should be preserved under [the `code-scanning` directory](https://github.com/actions/starter-workflows/tree/main/ci).
-- [ ] Should include a matching `code-scanning/properties/*.properties.json` file (for example, [`code-scanning/properties/codeql.properties.json`](https://github.com/actions/starter-workflows/blob/main/code-scanning/properties/codeql.properties.json)), with properties set as follows:
-  - [ ] `name`: Name of the Code Scanning integration.
-  - [ ] `organization`: Name of the organization producing the Code Scanning integration.
-  - [ ] `description`: Short description of the Code Scanning integration.
-  - [ ] `categories`: Array of languages supported by the Code Scanning integration.
-  - [ ] `iconName`: Name of the SVG logo representing the Code Scanning integration. This SVG logo must be present in [the `icons` directory](https://github.com/actions/starter-workflows/tree/main/icons).
-- [ ] 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` (for example, [`codeql.yml`](https://github.com/actions/starter-workflows/blob/c59b62dee0eae1f9f368b7011cf05c2fc42cf084/code-scanning/codeql.yml#L14-L21)).
-
-**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 require 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.

.github/workflows/label-feature.yml

@@ -1,21 +0,0 @@
-name: Close as a feature
-on:
-  issues:
-    types: [labeled]
-
-jobs:
-  build:
-    permissions:
-      issues: write
-    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.

.github/workflows/label-support.yml

@@ -1,21 +0,0 @@
-name: Close as a support issue
-on:
-  issues:
-    types: [labeled]
-
-jobs:
-  build:
-    permissions:
-      issues: write
-    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)

.github/workflows/labeler-triage.yml

@@ -1,16 +0,0 @@
-name: "Pull Request Labeler"
-
-permissions:
-  contents: read
-  pull-requests: write
-
-on:
-- pull_request_target
-
-jobs:
-  triage:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/labeler@v3
-      with:
-        repo-token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/stale.yml

@@ -1,22 +0,0 @@
-name: Mark stale issues and pull requests
-
-on:
-  schedule:
-  - cron: "21 4 * * *"
-
-jobs:
-  stale:
-
-    permissions:
-      issues: write
-      pull-requests: write
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/stale@v3
-      with:
-        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 

.github/workflows/sync_ghes.yaml

@@ -3,12 +3,10 @@ name: Sync workflows for GHES
 on:
   push:
     branches:
-    - main
+    - master
 
 jobs:
   sync:
-    permissions:
-      contents: write
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v2
@@ -16,7 +14,7 @@ jobs:
         git fetch --no-tags --prune --depth=1 origin +refs/heads/*:refs/remotes/origin/*
         git config user.email "cschleiden@github.com"
         git config user.name "GitHub Actions"
-    - uses: actions/setup-node@v2
+    - uses: actions/setup-node@v1
       with:
         node-version: '12'
     - name: Check starter workflows for GHES compat

.github/workflows/validate-data.yaml

@@ -5,14 +5,12 @@ on:
   pull_request:
 
 jobs:
-  validate-data:
-    permissions:
-      contents: read
+  sync:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
 
-      - uses: actions/setup-node@v2
+      - uses: actions/setup-node@v1
         with:
           node-version: "12"
 

CODEOWNERS

@@ -1,3 +0,0 @@
-* @actions/starter-workflows
-
-/code-scanning/ @actions/advanced-security-code-scanning

CONTRIBUTING.md

@@ -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 require 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

LICENSE

@@ -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.

README.md

@@ -10,39 +10,17 @@ These are the workflow files for helping people get started with GitHub Actions.
 
 <img src="https://d3vv6lp55qjaqc.cloudfront.net/items/353A3p3Y2x3c2t2N0c01/Image%202019-08-27%20at%203.25.07%20PM.png" max-width="75%"/>
 
-### Directory structure
-
-* [ci](ci): solutions for Continuous Integration and Deployments
+**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. This property is unique within the repository.
+**Valid properties:**
+* `name`: the name shown in onboarding
 * `description`: the description shown in onboarding
-* `iconName`: the icon name in the relevant folder, for example, `django` should have an icon `icons/django.svg`. Only SVG is supported at this time. Another option is to use [octicon](https://primer.style/octicons/). The format to use an octicon is `octicon <<icon name>>`. Example: `octicon person`
-* `creator`: creator of the template shown in onboarding. All the workflow templates from an author will have the same `creator` field.
-* `categories`: the categories that it will be shown under. Choose at least one category from the list [here](#categories). Further, choose the categories from the list of languages available [here](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). When a user views the available templates, those templates that match the same language will feature more prominently.
-
-### Categories
-* continuous-integration
-* deployment
-* testing
-* code-quality
-* code-review
-* dependency-management
-* monitoring
-* Automation
-* utilities
-
-### Variables
-These variables can be placed in the starter workflow and will be substituted as detailed below:
-
-* `$default-branch`: will substitute the branch from the repository, for example `main` and `master`
-* `$protected-branches`: will substitue any protected branches from the repository.
-* `$cron-daily`: will substitute a valid but random time within the day
+* `iconName`: the icon name in the relevant folder, for example `django` should have an icon `icons/django.svg`. Only SVG is supported at this time
+* `categories`: the categories that it will be shown under

automation/greetings.yml

@@ -1,3 +1,9 @@
+---
+name: Greetings
+description: Greets users who are first time contributors to the repo
+categories: [Automation, SDLC]
+iconName: octicon smiley
+---
 name: Greetings
 
 on: [pull_request, issues]
@@ -5,12 +11,9 @@ on: [pull_request, issues]
 jobs:
   greeting:
     runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      pull-requests: write
     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'
+        issue-message: 'Message that will be displayed on users'' first issue'
+        pr-message: 'Message that will be displayed on users'' first pr'

automation/label.yml

@@ -1,9 +1,15 @@
+---
+name: Labeler
+description: Labels pull requests based on the files changed
+categories: [Automation, SDLC]
+iconName: octicon tag
+---
 # 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
+# https://github.com/actions/labeler/blob/master/README.md
 
 name: Labeler
 on: [pull_request]
@@ -12,9 +18,6 @@ jobs:
   label:
 
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: write
 
     steps:
     - uses: actions/labeler@v2

automation/manual.yml

@@ -1,30 +0,0 @@
-# This is a basic workflow that is manually triggered
-
-name: Manual workflow
-
-# Controls when the action will run. Workflow runs when manually triggered using the UI
-# or API.
-on:
-  workflow_dispatch:
-    # Inputs the workflow accepts.
-    inputs:
-      name:
-        # Friendly description to be shown in the UI instead of 'name'
-        description: 'Person to greet'
-        # Default value if no value is explicitly provided
-        default: 'World'
-        # Input has to be provided for the workflow to run
-        required: true
-
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
-jobs:
-  # This workflow contains a single job called "greet"
-  greet:
-    # The type of runner that the job will run on
-    runs-on: ubuntu-latest
-
-    # Steps represent a sequence of tasks that will be executed as part of the job
-    steps:
-    # Runs a single command using the runners shell
-    - name: Send greeting
-      run: echo "Hello ${{ github.event.inputs.name }}"

automation/properties/greetings.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Greetings",
-    "description": "Greets users who are first time contributors to the repo",
-    "iconName": "octicon smiley",
-    "categories": ["Automation", "SDLC"]
-}

automation/properties/label.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Labeler",
-    "description": "Labels pull requests based on the files changed",
-    "iconName": "octicon tag",
-    "categories": ["Automation", "SDLC"]
-}

automation/properties/manual.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Manual workflow",
-    "description": "Simple workflow that is manually triggered.",
-    "iconName": "octicon person",
-    "categories": ["Automation"]
-}

automation/properties/stale.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Stale",
-    "description": "Checks for stale issues and pull requests",
-    "iconName": "octicon clock",
-    "categories": ["Automation", "SDLC"]
-}

automation/stale.yml

@@ -1,24 +1,22 @@
-# 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: Stale
+description: Checks for stale issues and pull requests
+categories: [Automation, SDLC]
+iconName: octicon clock
+---
 name: Mark stale issues and pull requests
 
 on:
   schedule:
-  - cron: $cron-daily
+  - cron: "0 0 * * *"
 
 jobs:
   stale:
 
     runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      pull-requests: write
 
     steps:
-    - uses: actions/stale@v3
+    - uses: actions/stale@v1
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
         stale-issue-message: 'Stale issue message'

ci/ada.yml

@@ -1,24 +0,0 @@
-name: Ada (GNAT)
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v2
-
-    - name: Set up GNAT toolchain
-      run: >
-        sudo apt-get update && 
-        sudo apt-get install gnat gprbuild
-
-    - name: Build
-      run: gprbuild -j0 -p

ci/android.yml

@@ -1,10 +1,16 @@
+---
+name: Android CI
+description: Build an Android project with Gradle.
+categories: [Java, Mobile]
+iconName: android
+---
 name: Android CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -13,14 +19,9 @@ jobs:
 
     steps:
     - uses: actions/checkout@v2
-    - name: set up JDK 11
-      uses: actions/setup-java@v2
+    - name: set up JDK 1.8
+      uses: actions/setup-java@v1
       with:
-        java-version: '11'
-        distribution: 'adopt'
-        cache: gradle
-
-    - name: Grant execute permission for gradlew
-      run: chmod +x gradlew
+        java-version: 1.8
     - name: Build with Gradle
       run: ./gradlew build

ci/ant.yml

@@ -1,3 +1,9 @@
+---
+name: Java with Ant
+description: Build and test a Java project with Apache Ant.
+categories: [Ant, Java]
+iconName: ant
+---
 # 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
 
@@ -5,9 +11,9 @@ name: Java CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -16,10 +22,9 @@ jobs:
 
     steps:
     - uses: actions/checkout@v2
-    - name: Set up JDK 11
-      uses: actions/setup-java@v2
+    - name: Set up JDK 1.8
+      uses: actions/setup-java@v1
       with:
-        java-version: '11'
-        distribution: 'adopt'
+        java-version: 1.8
     - name: Build with Ant
       run: ant -noinput -buildfile build.xml

ci/aws.yml

@@ -1,3 +1,9 @@
+---
+name: Deploy to Amazon ECS
+description: Deploy a container to an Amazon ECS service powered by AWS Fargate or Amazon EC2.
+categories: []
+iconName: aws
+---
 # 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
 #
@@ -33,7 +39,6 @@ jobs:
   deploy:
     name: Deploy
     runs-on: ubuntu-latest
-    environment: production
 
     steps:
     - name: Checkout
@@ -78,4 +83,4 @@ jobs:
         task-definition: ${{ steps.task-def.outputs.task-definition }}
         service: sample-app-service
         cluster: default
-        wait-for-service-stability: true
+        wait-for-service-stability: true

ci/azure.yml

@@ -1,3 +1,9 @@
+---
+name: Deploy Node.js to Azure Web App
+description: Build a Node.js project and deploy it to an Azure Web App.
+categories: []
+iconName: azure
+---
 # 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.
@@ -5,13 +11,10 @@
 #
 # 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.
+# 1. 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).
+# 2. 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
@@ -28,11 +31,10 @@ 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@v2
+      uses: actions/setup-node@v1
       with:
         node-version: ${{ env.NODE_VERSION }}
     - name: npm install, build, and test

ci/blank.yml

@@ -1,17 +1,20 @@
+---
+name: Simple workflow
+description: Start with a file with the minimum necessary structure.
+categories: []
+iconName: blank
+---
 # This is a basic workflow to help you get started with Actions
 
 name: CI
 
-# Controls when the workflow will run
+# Controls when the action will run. Triggers the workflow on push or pull request
+# events but only for the master branch
 on:
-  # Triggers the workflow on push or pull request events but only for the $default-branch branch
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
-
-  # Allows you to run this workflow manually from the Actions tab
-  workflow_dispatch:
+    branches: [ master ]
 
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
@@ -22,15 +25,15 @@ 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
+    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+    - uses: actions/checkout@v2
 
-      # Runs a single command using the runners shell
-      - name: Run a one-line script
-        run: echo Hello, world!
+    # Runs a single command using the runners shell
+    - name: Run a one-line script
+      run: echo Hello, world!
 
-      # Runs a set of commands using the runners shell
-      - name: Run a multi-line script
-        run: |
-          echo Add other actions to build,
-          echo test, and deploy your project.
+    # Runs a set of commands using the runners shell
+    - name: Run a multi-line script
+      run: |
+        echo Add other actions to build,
+        echo test, and deploy your project.

ci/c-cpp.yml

@@ -1,10 +1,16 @@
+---
+name: C/C++ with Make
+description: Build and test a C/C++ project using Make.
+categories: [C, C++]
+iconName: c-cpp
+---
 name: C/C++ CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

ci/clojure.yml

@@ -1,10 +1,16 @@
+---
+name: Clojure
+description: Build and test a Clojure project with Leiningen.
+categories: [Clojure, Java]
+iconName: clojure
+---
 name: Clojure CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

ci/cmake.yml

@@ -1,38 +0,0 @@
-name: CMake
-
-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@v2
-
-    - 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}}
-      

ci/crystal.yml

@@ -1,10 +1,16 @@
+---
+name: Crystal
+description: Build and test a Crystal project.
+categories: [Crystal]
+iconName: crystal
+---
 name: Crystal CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

ci/d.yml

@@ -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

ci/dart.yml

@@ -1,42 +1,28 @@
-# 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: Dart
+description: Build and test a Dart project with Pub.
+categories: [Dart]
+iconName: dart
+---
+name: Dart CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
+
     runs-on: ubuntu-latest
 
+    container:
+      image:  google/dart:latest
+
     steps:
-      - uses: actions/checkout@v2
-
-      # Note: This workflow uses the latest stable version of the Dart SDK.
-      # You can specify other versions if desired, see documentation here:
-      # https://github.com/dart-lang/setup-dart/blob/main/README.md
-      # - uses: dart-lang/setup-dart@v1
-      - uses: dart-lang/setup-dart@9a04e6d73cca37bd455e0608d7e5092f881fd603
-
-      - 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
+    - uses: actions/checkout@v2
+    - name: Install dependencies
+      run: pub get
+    - name: Run tests
+      run: pub run test

ci/deno.yml

@@ -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 then run Deno lint and test.
-# For more information see: https://github.com/denoland/setup-deno
-
-name: Deno
-
-on:
-  push:
-    branches: [$default-branch]
-  pull_request:
-    branches: [$default-branch]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Setup repo
-        uses: actions/checkout@v2
-
-      - name: Setup Deno
-        # uses: denoland/setup-deno@v1
-        uses: denoland/setup-deno@004814556e37c54a2f6e31384c9e18e9833173669
-        with:
-          deno-version: v1.x
-
-      # Uncomment this step to verify the use of 'deno fmt' on each commit.
-      # - name: Verify formatting
-      #   run: deno fmt --check
-
-      - name: Run linter
-        run: deno lint
-
-      - name: Run tests
-        run: deno test -A --unstable

ci/django.yml

@@ -1,10 +1,16 @@
+---
+name: Django
+description: Build and Test a Django Project
+categories: [Python, Django]
+iconName: django
+---
 name: Django CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -13,12 +19,12 @@ jobs:
     strategy:
       max-parallel: 4
       matrix:
-        python-version: [3.7, 3.8, 3.9]
+        python-version: [3.6, 3.7, 3.8]
 
     steps:
     - uses: actions/checkout@v2
     - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
+      uses: actions/setup-python@v1
       with:
         python-version: ${{ matrix.python-version }}
     - name: Install Dependencies

ci/docker-image.yml

@@ -1,10 +1,16 @@
+---
+name: Docker image
+description: Build a Docker image to deploy, run, or push to a registry.
+categories: [Dockerfile]
+iconName: docker
+---
 name: Docker Image CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
 

ci/docker-publish.yml

@@ -1,63 +1,82 @@
+---
+name: Publish Docker Container
+description: Build, test and push Docker image to GitHub Packages.
+categories: [Dockerfile]
+iconName: docker
+---
 name: Docker
 
-# 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.
-
 on:
-  schedule:
-    - cron: $cron-daily
   push:
-    branches: [ $default-branch ]
-    # Publish semver tags as releases.
-    tags: [ 'v*.*.*' ]
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
   pull_request:
-    branches: [ $default-branch ]
 
 env:
-  # Use docker.io for Docker Hub if empty
-  REGISTRY: ghcr.io
-  # github.repository as <account>/<repo>
-  IMAGE_NAME: ${{ github.repository }}
-
+  # TODO: Change variable to your image's name.
+  IMAGE_NAME: image
 
 jobs:
-  build:
-
+  # Run tests.
+  # See also https://docs.docker.com/docker-hub/builds/automated-testing/
+  test:
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
 
     steps:
-      - name: Checkout repository
-        uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-      # Login against a Docker registry except on PR
-      # https://github.com/docker/login-action
-      - name: Log into registry ${{ env.REGISTRY }}
-        if: github.event_name != 'pull_request'
-        uses: docker/login-action@28218f9b04b4f3f62068d7b6ce6ca5b26e35336c
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+      - 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
 
-      # Extract metadata (tags, labels) for Docker
-      # https://github.com/docker/metadata-action
-      - name: Extract Docker metadata
-        id: meta
-        uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
-        with:
-          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    # Ensure test job passes before pushing image.
+    needs: test
 
-      # Build and push Docker image with Buildx (don't push on PR)
-      # https://github.com/docker/build-push-action
-      - name: Build and push Docker image
-        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
-        with:
-          context: .
-          push: ${{ github.event_name != 'pull_request' }}
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}
+    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" == "master" ] && VERSION=latest
+
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION

ci/dotnet-core.yml

@@ -0,0 +1,31 @@
+---
+name: .NET Core
+description: Build and test a .NET Core or ASP.NET Core project.
+categories: [C#, F#, Visual Basic, ASP, ASP.NET, .NET]
+iconName: dotnetcore
+---
+name: .NET Core
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Setup .NET Core
+      uses: actions/setup-dotnet@v1
+      with:
+        dotnet-version: 3.1.101
+    - name: Install dependencies
+      run: dotnet restore
+    - name: Build
+      run: dotnet build --configuration Release --no-restore
+    - name: Test
+      run: dotnet test --no-restore --verbosity normal

ci/dotnet.yml

@@ -1,25 +0,0 @@
-name: .NET
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET
-      uses: actions/setup-dotnet@v1
-      with:
-        dotnet-version: 5.0.x
-    - name: Restore dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --no-restore
-    - name: Test
-      run: dotnet test --no-build --verbosity normal

ci/elixir.yml

@@ -1,31 +1,30 @@
-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: erlef/setup-elixir@885971a72ed1f9240973bd92ab57af8c1aa68f24
-      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
+---
+name: Elixir
+description: Build and test an Elixir project with Mix.
+categories: [Elixir, Erlang]
+iconName: elixir
+---
+name: Elixir CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Setup elixir
+      uses: actions/setup-elixir@v1
+      with:
+        elixir-version: 1.9.4 # Define the elixir version [required]
+        otp-version: 22.2 # Define the OTP version [required]
+    - name: Install Dependencies
+      run: mix deps.get
+    - name: Run Tests
+      run: mix test

ci/erlang.yml

@@ -1,10 +1,16 @@
+---
+name: Erlang
+description: Build and test an Erlang project with rebar.
+categories: [Erlang]
+iconName: erlang
+---
 name: Erlang CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
 

ci/gem-push.yml

@@ -1,37 +1,40 @@
+---
+name: Ruby Gem
+description: Pushes a Ruby Gem to RubyGems and GitHub Package Registry.
+categories: [Ruby, SDLC]
+iconName: ruby-gems
+---
 name: Ruby Gem
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
     name: Build + Publish
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
 
     steps:
     - uses: actions/checkout@v2
     - name: Set up Ruby 2.6
       uses: actions/setup-ruby@v1
       with:
-        ruby-version: 2.6.x
+        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
+        printf -- "---\n:github: Bearer ${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 }}
+        GEM_HOST_API_KEY: ${{secrets.GPR_AUTH_TOKEN}}
+        OWNER: username
 
     - name: Publish to RubyGems
       run: |
@@ -42,4 +45,4 @@ jobs:
         gem build *.gemspec
         gem push *.gem
       env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+        GEM_HOST_API_KEY: ${{secrets.RUBYGEMS_AUTH_TOKEN}}

ci/go.yml

@@ -1,25 +1,43 @@
+---
+name: Go
+description: Build a Go project.
+categories: [Go]
+iconName: go
+---
 name: Go
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
 
   build:
+    name: Build
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
 
-    - name: Set up Go
+    - name: Set up Go 1.x
       uses: actions/setup-go@v2
       with:
-        go-version: 1.17
+        go-version: ^1.13
+      id: go
+
+    - name: Check out code into the Go module directory
+      uses: actions/checkout@v2
+
+    - name: Get dependencies
+      run: |
+        go get -v -t -d ./...
+        if [ -f Gopkg.toml ]; then
+            curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh
+            dep ensure
+        fi
 
     - name: Build
-      run: go build -v ./...
+      run: go build -v .
 
     - name: Test
-      run: go test -v ./...
+      run: go test -v .

ci/google.yml

@@ -0,0 +1,81 @@
+---
+name: Build and Deploy to GKE
+description: Build a docker container, publish it to Google Container Registry, and deploy to GKE.
+categories: []
+iconName: googlegke
+---
+# 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, GKE_EMAIL with the service account email, GKE_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, REGISTRY_HOSTNAME and DEPLOYMENT_NAME environment variables (below).
+
+name: Build and Deploy to GKE
+
+on:
+  release:
+    types: [created]
+
+# Environment variables available to all jobs and steps in this workflow
+env:
+  GKE_PROJECT: ${{ secrets.GKE_PROJECT }}
+  GKE_EMAIL: ${{ secrets.GKE_EMAIL }}
+  GITHUB_SHA: ${{ github.sha }}
+  GKE_ZONE: us-west1-a
+  GKE_CLUSTER: example-gke-cluster
+  IMAGE: gke-test
+  REGISTRY_HOSTNAME: gcr.io
+  DEPLOYMENT_NAME: gke-test
+
+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: GoogleCloudPlatform/github-actions/setup-gcloud@master
+      with:
+        version: '270.0.0'
+        service_account_email: ${{ secrets.GKE_EMAIL }}
+        service_account_key: ${{ secrets.GKE_KEY }}
+
+    # Configure docker to use the gcloud command-line tool as a credential helper
+    - run: |
+        # Set up docker to authenticate
+        # via gcloud command-line tool.
+        gcloud auth configure-docker
+      
+    # Build the Docker image
+    - name: Build
+      run: |        
+        docker build -t "$REGISTRY_HOSTNAME"/"$GKE_PROJECT"/"$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 $REGISTRY_HOSTNAME/$GKE_PROJECT/$IMAGE:$GITHUB_SHA
+        
+    # Set up kustomize
+    - name: Set up Kustomize
+      run: |
+        curl -o kustomize --location 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: |
+        gcloud container clusters get-credentials $GKE_CLUSTER --zone $GKE_ZONE --project $GKE_PROJECT
+        ./kustomize edit set image $REGISTRY_HOSTNAME/$GKE_PROJECT/$IMAGE:${GITHUB_SHA}
+        ./kustomize build . | kubectl apply -f -
+        kubectl rollout status deployment/$DEPLOYMENT_NAME
+        kubectl get services -o wide

ci/gradle-publish.yml

@@ -1,5 +1,11 @@
+---
+name: Publish Java Package with Gradle
+description: Build a Java Package using Gradle and publish to GitHub Packages.
+categories: [Java, Gradle]
+iconName: gradle
+---
 # 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/blob/main/docs/advanced-usage.md#Publishing-using-gradle
+# For more information see: https://github.com/actions/setup-java#publishing-using-gradle
 
 name: Gradle Package
 
@@ -11,17 +17,13 @@ jobs:
   build:
 
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
 
     steps:
     - uses: actions/checkout@v2
-    - name: Set up JDK 11
-      uses: actions/setup-java@v2
+    - name: Set up JDK 1.8
+      uses: actions/setup-java@v1
       with:
-        java-version: '11'
-        distribution: 'adopt'
+        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
 

ci/gradle.yml

@@ -1,13 +1,19 @@
-# This workflow will build a Java project with Gradle and cache/restore any dependencies to improve the workflow execution time
+---
+name: Java with Gradle
+description: Build and test a Java project using a Gradle wrapper script.
+categories: [Java, Gradle]
+iconName: gradle
+---
+# 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 ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -16,12 +22,10 @@ jobs:
 
     steps:
     - uses: actions/checkout@v2
-    - name: Set up JDK 11
-      uses: actions/setup-java@v2
+    - name: Set up JDK 1.8
+      uses: actions/setup-java@v1
       with:
-        java-version: '11'
-        distribution: 'adopt'
-        cache: gradle
+        java-version: 1.8
     - name: Grant execute permission for gradlew
       run: chmod +x gradlew
     - name: Build with Gradle

ci/haskell.yml

@@ -1,10 +1,16 @@
+---
+name: Haskell
+description: Build and test a Haskell project with Cabal.
+categories: [Haskell]
+iconName: haskell
+---
 name: Haskell CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -15,8 +21,8 @@ jobs:
     - uses: actions/checkout@v2
     - uses: actions/setup-haskell@v1
       with:
-        ghc-version: '8.10.3'
-        cabal-version: '3.2'
+        ghc-version: '8.8.2'
+        cabal-version: '3.0'
 
     - name: Cache
       uses: actions/cache@v1

ci/ibm.yml

@@ -1,3 +1,9 @@
+---
+name: Build and Deploy to IKS
+description: Build a docker container, publish it to IBM Container Registry, and deploy to IKS.
+categories: []
+iconName: ibm
+---
 # 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:
@@ -28,7 +34,6 @@ jobs:
   setup-build-publish-deploy:
     name: Setup, Build, Publish, and Deploy
     runs-on: ubuntu-latest
-    environment: production
     steps:
 
     - name: Checkout

ci/ios.yml

@@ -1,44 +0,0 @@
-name: iOS starter workflow
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-    name: Build and Test default scheme using any available iPhone simulator
-    runs-on: macos-latest
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-      - 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' }}
-          platform: ${{ 'iOS Simulator' }}
-        run: |
-          # 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}'`
-          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 build-for-testing -scheme "$scheme" -"$filetype_parameter" "$file_to_build" -destination "platform=$platform,name=$device"
-      - name: Test
-        env:
-          scheme: ${{ 'default' }}
-          platform: ${{ 'iOS Simulator' }}
-        run: |
-          # 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}'`
-          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 test-without-building -scheme "$scheme" -"$filetype_parameter" "$file_to_build" -destination "platform=$platform,name=$device"

ci/jekyll.yml

@@ -1,10 +1,16 @@
+---
+name: Jekyll
+description: Package a Jekyll site using the jekyll/builder Docker image.
+categories: [HTML]
+iconName: jekyll
+---
 name: Jekyll site CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -17,4 +23,4 @@ jobs:
       run: |
         docker run \
         -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
-        jekyll/builder:latest /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future"
+        jekyll/builder:latest /bin/bash -c "chmod 777 /srv/jekyll && jekyll build --future"

ci/laravel.yml

@@ -1,25 +1,28 @@
+---
+name: Laravel
+description: Test a Laravel project.
+categories: [PHP, Laravel]
+iconName: php
+---
 name: Laravel
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   laravel-tests:
 
     runs-on: ubuntu-latest
-
+    
     steps:
-    - uses: shivammathur/setup-php@15c43e89cdef867065b0213be354c2841860869e
-      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
+      run: composer install -q --no-ansi --no-interaction --no-scripts --no-suggest --no-progress --prefer-dist
     - name: Generate key
       run: php artisan key:generate
     - name: Directory Permissions

ci/makefile.yml

@@ -1,27 +0,0 @@
-name: Makefile CI
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v2
-    
-    - name: configure
-      run: ./configure
-      
-    - name: Install dependencies
-      run: make
-      
-    - name: Run check
-      run: make check
-      
-    - name: Run distcheck
-      run: make distcheck

ci/maven-publish.yml

@@ -1,5 +1,11 @@
+---
+name: Publish Java Package with Maven
+description: Build a Java Package using Maven and publish to GitHub Packages.
+categories: [Java, Maven]
+iconName: maven
+---
 # 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/blob/main/docs/advanced-usage.md#apache-maven-with-a-settings-path
+# For more information see: https://github.com/actions/setup-java#apache-maven-with-a-settings-path
 
 name: Maven Package
 
@@ -11,17 +17,13 @@ jobs:
   build:
 
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
 
     steps:
     - uses: actions/checkout@v2
-    - name: Set up JDK 11
-      uses: actions/setup-java@v2
+    - name: Set up JDK 1.8
+      uses: actions/setup-java@v1
       with:
-        java-version: '11'
-        distribution: 'adopt'
+        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
 
@@ -31,4 +33,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 }}

ci/maven.yml

@@ -1,13 +1,19 @@
-# This workflow will build a Java project with Maven, and cache/restore any dependencies to improve the workflow execution time
+---
+name: Java with Maven
+description: Build and test a Java project with Apache Maven.
+categories: [Java, Maven]
+iconName: maven
+---
+# 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 ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -16,11 +22,9 @@ jobs:
 
     steps:
     - uses: actions/checkout@v2
-    - name: Set up JDK 11
-      uses: actions/setup-java@v2
+    - name: Set up JDK 1.8
+      uses: actions/setup-java@v1
       with:
-        java-version: '11'
-        distribution: 'adopt'
-        cache: maven
+        java-version: 1.8
     - name: Build with Maven
       run: mvn -B package --file pom.xml

ci/msbuild.yml

@@ -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.0.2
-
-    - 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}}

ci/node.js.yml

@@ -1,13 +1,19 @@
-# This workflow will do a clean install of node dependencies, cache/restore them, build the source code and run tests across different versions of node
+---
+name: Node.js
+description: Build and test a Node.js project with npm.
+categories: [JavaScript, Node, Npm]
+iconName: nodejs
+---
+# 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
 
 name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -16,16 +22,14 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [12.x, 14.x, 16.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
+        node-version: [10.x, 12.x]
 
     steps:
     - uses: actions/checkout@v2
     - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v2
+      uses: actions/setup-node@v1
       with:
         node-version: ${{ matrix.node-version }}
-        cache: 'npm'
     - run: npm ci
     - run: npm run build --if-present
     - run: npm test

ci/npm-grunt.yml

@@ -1,28 +0,0 @@
-name: NodeJS with Grunt
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-
-    strategy:
-      matrix:
-        node-version: [12.x, 14.x, 16.x]
-    
-    steps:
-    - uses: actions/checkout@v2
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-
-    - name: Build
-      run: |
-        npm install
-        grunt

ci/npm-gulp.yml

@@ -1,28 +0,0 @@
-name: NodeJS with Gulp
-
-on:
-  push:
-    branches: [ $default-branch ]
-  pull_request:
-    branches: [ $default-branch ]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-
-    strategy:
-      matrix:
-        node-version: [12.x, 14.x, 16.x]
-    
-    steps:
-    - uses: actions/checkout@v2
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-
-    - name: Build
-      run: |
-        npm install
-        gulp

ci/npm-publish.yml

@@ -1,3 +1,9 @@
+---
+name: Publish Node.js Package
+description: Publishes a Node.js package to npm and GitHub Packages.
+categories: [JavaScript, SDLC]
+iconName: node-package-transparent
+---
 # 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
 
@@ -12,9 +18,9 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
+      - uses: actions/setup-node@v1
         with:
-          node-version: 14
+          node-version: 12
       - run: npm ci
       - run: npm test
 
@@ -23,9 +29,9 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
+      - uses: actions/setup-node@v1
         with:
-          node-version: 14
+          node-version: 12
           registry-url: https://registry.npmjs.org/
       - run: npm ci
       - run: npm publish
@@ -35,15 +41,12 @@ jobs:
   publish-gpr:
     needs: build
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
     steps:
       - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
+      - uses: actions/setup-node@v1
         with:
-          node-version: 14
-          registry-url: $registry-url(npm)
+          node-version: 12
+          registry-url: https://npm.pkg.github.com/
       - run: npm ci
       - run: npm publish
         env:

ci/php.yml

@@ -1,10 +1,16 @@
+---
+name: PHP
+description: Build and test a PHP application using Composer
+categories: [PHP, Composer]
+iconName: php
+---
 name: PHP Composer
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -15,16 +21,7 @@ jobs:
     - uses: actions/checkout@v2
 
     - name: Validate composer.json and composer.lock
-      run: composer validate --strict
-
-    - name: Cache Composer packages
-      id: composer-cache
-      uses: actions/cache@v2
-      with:
-        path: vendor
-        key: ${{ runner.os }}-php-${{ hashFiles('**/composer.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-php-
+      run: composer validate
 
     - name: Install dependencies
       run: composer install --prefer-dist --no-progress

ci/properties/ada.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Ada",
-    "description": "Build Ada project with GPRbuild.",
-    "iconName": "ada",
-    "categories": ["Continuous integration", "Ada"]
-}

ci/properties/android.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Android CI",
-    "description": "Build an Android project with Gradle.",
-    "iconName": "android",
-    "categories": ["Continuous integration", "Java", "Mobile"]
-}

ci/properties/ant.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Java with Ant",
-    "description": "Build and test a Java project with Apache Ant.",
-    "iconName": "ant",
-    "categories": ["Continuous integration", "Ant", "Java"]
-}

ci/properties/blank.properties.json

@@ -1,7 +0,0 @@
-{
-    "name": "Simple workflow",
-    "description": "Start with a file with the minimum necessary structure.",
-    "creator": "GitHub",
-    "iconName": "blank",
-    "categories": null
-}

ci/properties/c-cpp.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "C/C++ with Make",
-    "description": "Build and test a C/C++ project using Make.",
-    "iconName": "c-cpp",
-    "categories": ["Continuous integration", "C", "C++"]
-}

ci/properties/clojure.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Clojure",
-    "description": "Build and test a Clojure project with Leiningen.",
-    "iconName": "clojure",
-    "categories": ["Continuous integration", "Clojure", "Java"]
-}

ci/properties/cmake.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "CMake based projects",
-    "description": "Build and test a CMake based project.",
-    "iconName": "cmake",
-    "categories": ["Continuous integration", "C", "C++"]
-}

ci/properties/crystal.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Crystal",
-    "description": "Build and test a Crystal project.",
-    "iconName": "crystal",
-    "categories": ["Continuous integration", "Crystal"]
-}

ci/properties/d.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "D",
-    "description": "Build and test a D project with dub.",
-    "iconName": "d",
-    "categories": ["Continuous integration", "D"]
-}

ci/properties/dart.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Dart",
-    "description": "Build and test a Dart project with Pub.",
-    "iconName": "dart",
-    "categories": ["Continuous integration", "Dart"]
-}

ci/properties/deno.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Deno",
-    "description": "Test your Deno project",
-    "iconName": "deno",
-    "categories": ["Continuous integration", "JavaScript", "TypeScript", "Deno"]
-}

ci/properties/django.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Django",
-    "description": "Build and Test a Django Project",
-    "iconName": "django",
-    "categories": ["Continuous integration", "Python", "Django"]
-}

ci/properties/docker-image.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Docker image",
-    "description": "Build a Docker image to deploy, run, or push to a registry.",
-    "iconName": "docker",
-    "categories": ["Continuous integration", "Dockerfile"]
-}

ci/properties/docker-publish.properties.json

@@ -1,6 +0,0 @@
-{
-  "name": "Publish Docker Container",
-  "description": "Build, test and push Docker image to GitHub Packages.",
-  "iconName": "docker",
-  "categories": ["Continuous integration", "Dockerfile"]
-}

ci/properties/dotnet-desktop.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": ".NET Desktop",
-    "description": "Build, test, sign and publish a desktop application built on .NET.",
-    "iconName": "dotnet",
-    "categories": ["Continuous integration", "C#", "Visual Basic", "WPF", ".NET"]
-}

ci/properties/dotnet.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": ".NET",
-    "description": "Build and test a .NET or ASP.NET Core project.",
-    "iconName": "dotnet",
-    "categories": ["Continuous integration", "C#", "F#", "Visual Basic", "ASP", "ASP.NET", ".NET", "AspNetCore", "DotNetConsole"]
-}

ci/properties/elixir.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Elixir",
-    "description": "Build and test an Elixir project with Mix.",
-    "iconName": "elixir",
-    "categories": ["Continuous integration", "Elixir", "Erlang"]
-}

ci/properties/erlang.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Erlang",
-    "description": "Build and test an Erlang project with rebar.",
-    "iconName": "erlang",
-    "categories": ["Continuous integration", "Erlang"]
-}

ci/properties/gem-push.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Ruby Gem",
-    "description": "Pushes a Ruby Gem to RubyGems and GitHub Package Registry.",
-    "iconName": "ruby-gems",
-    "categories": ["Continuous integration", "Ruby"]
-}

ci/properties/go.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Go",
-    "description": "Build a Go project.",
-    "iconName": "go",
-    "categories": ["Continuous integration", "Go"]
-}

ci/properties/gradle-publish.properties.json

@@ -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": ["Continuous integration", "Java", "Gradle", "Spring", "JSF"]
-}

ci/properties/gradle.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Java with Gradle",
-    "description": "Build and test a Java project using a Gradle wrapper script.",
-    "iconName": "gradle",
-    "categories": ["Continuous integration", "Java", "Gradle", "Spring", "JSF"]
-}

ci/properties/haskell.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Haskell",
-    "description": "Build and test a Haskell project with Cabal.",
-    "iconName": "haskell",
-    "categories": ["Continuous integration", "Haskell"]
-}

ci/properties/ios.properties.json

@@ -1,10 +0,0 @@
-{
-    "name": "iOS",
-    "description": "Build and test an iOS application using xcodebuild and any available iPhone simulator.",
-    "iconName": "xcode",
-    "categories": [
-        "Continuous integration",
-        "iOS",
-        "Xcode"
-    ]
-}

ci/properties/jekyll.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Jekyll",
-    "description": "Package a Jekyll site using the jekyll/builder Docker image.",
-    "iconName": "jekyll",
-    "categories": ["Continuous integration", "HTML"]
-}

ci/properties/laravel.properties.json

@@ -1,10 +0,0 @@
-{
-    "name": "Laravel",
-    "description": "Test a Laravel project.",
-    "iconName": "php",
-    "categories": [
-        "Continuous integration",
-        "PHP",
-        "Laravel"
-    ]
-}

ci/properties/makefile.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Build projects with Make",
-    "description": "Build and test a project using Make.",
-    "iconName": "makefile",
-    "categories": ["Continuous integration", "Makefile"]
-}

ci/properties/maven-publish.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Publish Java Package with Maven",
-    "description": "Build a Java Package using Maven and publish to GitHub Packages.",
-    "iconName": "maven",
-    "categories": ["Continuous integration", "Java", "Maven", "Spring", "JSF"]
-}

ci/properties/maven.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Java with Maven",
-    "description": "Build and test a Java project with Apache Maven.",
-    "iconName": "maven",
-    "categories": ["Continuous integration", "Java", "Maven", "Spring", "JSF"]
-}

ci/properties/msbuild.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "MSBuild based projects",
-    "description": "Build a MSBuild based project.",
-    "iconName": "c-cpp",
-    "categories": ["Continuous integration", "C", "C++"]
-}

ci/properties/node.js.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Node.js",
-    "description": "Build and test a Node.js project with npm.",
-    "iconName": "nodejs",
-    "categories": ["Continuous integration", "JavaScript", "npm", "React", "Angular"]
-}

ci/properties/npm-grunt.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Grunt",
-    "description": "Build a NodeJS project with npm and grunt.",
-    "iconName": "grunt",
-    "categories": ["Continuous integration", "JavaScript", "TypeScript", "npm", "Grunt"]
-}

ci/properties/npm-gulp.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Gulp",
-    "description": "Build a NodeJS project with npm and gulp.",
-    "iconName": "gulp",
-    "categories": ["Continuous integration", "JavaScript", "TypeScript", "npm", "Gulp"]
-}

ci/properties/npm-publish.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Publish Node.js Package",
-    "description": "Publishes a Node.js package to npm and GitHub Packages.",
-    "iconName": "node-package-transparent",
-    "categories": ["Continuous integration", "JavaScript", "npm"]
-}

ci/properties/php.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "PHP",
-    "description": "Build and test a PHP application using Composer",
-    "iconName": "php",
-    "categories": ["Continuous integration", "PHP", "Composer"]
-}

ci/properties/pylint.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Pylint",
-    "description": "Lint a Python application with pylint.",
-    "iconName": "python",
-    "categories": ["Continuous integration", "Python", "Bottle", "Flask"]
-}

ci/properties/python-app.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Python application",
-    "description": "Create and test a Python application.",
-    "iconName": "python",
-    "categories": ["Continuous integration", "Python", "Bottle", "Flask"]
-}

ci/properties/python-package-conda.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Python Package using Anaconda",
-    "description": "Create and test a Python package on multiple Python versions using Anaconda for package management.",
-    "iconName": "python",
-    "categories": ["Continuous integration", "Python"]
-}

ci/properties/python-package.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Python package",
-    "description": "Create and test a Python package on multiple Python versions.",
-    "iconName": "python",
-    "categories": ["Continuous integration", "Python", "Bottle", "Flask"]
-}

ci/properties/python-publish.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Publish Python Package",
-    "description": "Publish a Python Package to PyPI on release.",
-    "iconName": "python",
-    "categories": ["Continuous integration", "Python"]
-}

ci/properties/r.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "R package",
-    "description": "Create and test an R package on multiple R versions.",
-    "iconName": "r",
-    "categories": ["Continuous integration", "R"]
-}