Remove properties.

.github/pull_request_template.md

@@ -1,17 +1,7 @@
-This repository contains configuration for what users see when they click on the `Actions` tab.
+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
-
----
-
-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.
-
-Please **add to this description** at the bottom :point_down:
-
-- [ ] A good description of the workflow at the bottom of this page.
-- [ ] Some links to the language or tool will be nice (unless its really obvious)
+- [ ] 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:
 
@@ -23,12 +13,14 @@ In the workflow and properties files:
 - [ ] 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 ]`.
+
+  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).  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 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

.github/workflows/label-close.yml

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

.github/workflows/validate-data.yaml

@@ -5,7 +5,7 @@ on:
   pull_request:
 
 jobs:
-  validate-data:
+  sync:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2

README.md

@@ -17,7 +17,7 @@ These are the workflow files for helping people get started with GitHub Actions.
 
 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/python-django.yml` and `ci/properties/python-django.properties.json`.
+For example: `ci/python-django.yml` and `ci/python-django.properties.json`.
 
 **Valid properties:**
 * `name`: the name shown in onboarding

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]

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]

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": "blank",
-    "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,8 +1,14 @@
+---
+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: "30 1 * * *"
+  - cron: "0 0 * * *"
 
 jobs:
   stale:

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:

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:

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
 #

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.

ci/blank.yml

@@ -1,14 +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 action will run. Triggers the workflow on push or pull request
-# events but only for the $default-branch branch
+# events but only for the master branch
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:

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/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/dart.yml

@@ -1,10 +1,16 @@
+---
+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:

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:

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,10 +1,16 @@
+---
+name: Publish Docker Container
+description: Build, test and push Docker image to GitHub Packages.
+categories: [Dockerfile]
+iconName: docker
+---
 name: Docker
 
 on:
   push:
-    # Publish `$default-branch` as Docker `latest` image.
+    # Publish `master` as Docker `latest` image.
     branches:
-      - $default-branch
+      - master
 
     # Publish `v1.2.3` tags as releases.
     tags:
@@ -56,7 +62,7 @@ jobs:
       - 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]')
 
@@ -67,7 +73,7 @@ jobs:
           [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
 
           # Use Docker `latest` tag convention
-          [ "$VERSION" == "$default-branch" ] && VERSION=latest
+          [ "$VERSION" == "master" ] && VERSION=latest
 
           echo IMAGE_ID=$IMAGE_ID
           echo VERSION=$VERSION

ci/dotnet-core.yml

@@ -1,10 +1,16 @@
+---
+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: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

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: 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
+---
+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,10 +1,16 @@
+---
+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:

ci/go.yml

@@ -1,10 +1,16 @@
+---
+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:
 

ci/google.yml

@@ -1,3 +1,9 @@
+---
+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:

ci/gradle-publish.yml

@@ -1,3 +1,9 @@
+---
+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#publishing-using-gradle
 

ci/gradle.yml

@@ -1,3 +1,9 @@
+---
+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
 
@@ -5,9 +11,9 @@ name: Java CI with Gradle
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

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:

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:

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:

ci/laravel.yml

@@ -1,22 +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: 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/maven-publish.yml

@@ -1,3 +1,9 @@
+---
+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#apache-maven-with-a-settings-path
 

ci/maven.yml

@@ -1,3 +1,9 @@
+---
+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
 
@@ -5,9 +11,9 @@ name: Java CI with Maven
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

ci/node.js.yml

@@ -1,3 +1,9 @@
+---
+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
 
@@ -5,9 +11,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:
@@ -16,7 +22,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [10.x, 12.x, 14.x]
+        node-version: [10.x, 12.x]
 
     steps:
     - uses: actions/checkout@v2

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
 

ci/phoenix.yml

@@ -1,46 +0,0 @@
-name: Phoenix
-
-on:
-  push:
-    branches: [$default-branch]
-  pull_request:
-    branches: [$default-branch]
-
-jobs:
-  build:
-    name: Build and test
-    runs-on: ubuntu-latest
-    env: {MIX_ENV: test}
-
-    services:
-      postgres:
-        image: postgres:13
-        env:
-          POSTGRES_USER: postgres
-          POSTGRES_PASSWORD: postgres
-          # NOTE: Replace "phoenix_test" with your DB name from config/test.exs.
-          POSTGRES_DB: phoenix_test
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-        ports: ['5432:5432']
-
-    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

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:
@@ -17,18 +23,8 @@ jobs:
     - name: Validate composer.json and composer.lock
       run: composer validate
 
-    - 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-
-
     - 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

ci/properties/android.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Android CI",
-    "description": "Build an Android project with Gradle.",
-    "iconName": "android",
-    "categories": ["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": ["Ant", "Java"]
-}

ci/properties/aws.properties.json

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

ci/properties/azure.properties.json

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

ci/properties/blank.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Simple workflow",
-    "description": "Start with a file with the minimum necessary structure.",
-    "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": ["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": ["Clojure", "Java"]
-}

ci/properties/crystal.properties.json

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

ci/properties/dart.properties.json

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

ci/properties/django.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Django",
-    "description": "Build and Test a Django Project",
-    "iconName": "django",
-    "categories": ["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": ["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": ["Dockerfile"]
-}

ci/properties/dotnet-core-desktop.properties.json

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

ci/properties/dotnet-core.properties.json

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

ci/properties/elixir.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Elixir",
-    "description": "Build and test an Elixir project with Mix.",
-    "iconName": "elixir",
-    "categories": ["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": ["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": ["Ruby", "SDLC"]
-}

ci/properties/go.properties.json

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

ci/properties/google.properties.json

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

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": ["Java", "Gradle"]
-}

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": ["Java", "Gradle"]
-}

ci/properties/haskell.properties.json

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

ci/properties/ibm.properties.json

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

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": ["HTML"]
-}

ci/properties/laravel.properties.json

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

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": ["Java", "Maven"]
-}

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": ["Java", "Maven"]
-}

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": ["JavaScript", "Node", "Npm"]
-}

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": ["JavaScript", "SDLC"]
-}

ci/properties/phoenix.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Phoenix",
-    "description": "Build and test an Elixir Phoenix project.",
-    "iconName": "phoenix",
-    "categories": ["Elixir", "Erlang", "Phoenix"]
-}

ci/properties/php.properties.json

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

ci/properties/python-app.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Python application",
-    "description": "Create and test a Python application.",
-    "iconName": "python",
-    "categories": ["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": ["Python"]
-}

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": ["Python"]
-}

ci/properties/ruby.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Ruby",
-    "description": "Build and test a Ruby project with Rake.",
-    "iconName": "ruby",
-    "categories": ["Ruby"]
-}

ci/properties/rust.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Rust",
-    "description": "Build and test a Rust project with Cargo.",
-    "iconName": "rust",
-    "categories": ["Rust"]
-}

ci/properties/scala.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Scala",
-    "description": "Build and test a Scala project with SBT.",
-    "iconName": "scala",
-    "categories": ["Scala", "Java"]
-}

ci/properties/swift.properties.json

@@ -1,6 +0,0 @@
-{
-    "name": "Swift",
-    "description": "Build and test a Swift Package.",
-    "iconName": "swift",
-    "categories": ["Swift"]
-}

ci/properties/tencent.properties.json

@@ -1,7 +0,0 @@
-{
-    "name": "Tencent Kubernetes Engine",
-    "description": "This workflow will build a docker container, publish and deploy it to Tencent Kubernetes Engine (TKE).",
-    "creator": "Tencent Cloud",
-    "iconName": "tencentcloud",
-    "categories": null
-}

ci/properties/terraform.properties.json

@@ -1,7 +0,0 @@
-{
-    "name": "Terraform",
-    "description": "Set up Terraform CLI in your GitHub Actions workflow.",
-    "creator": "HashiCorp",
-    "iconName": "terraform",
-    "categories": null
-}

ci/python-app.yml

@@ -1,3 +1,9 @@
+---
+name: Python application
+description: Create and test a Python application.
+categories: [Python]
+iconName: python
+---
 # This workflow will install Python dependencies, run tests and lint with a single version of Python
 # For more information see: https://help.github.com/actions/language-and-framework-guides/using-python-with-github-actions
 
@@ -5,9 +11,9 @@ name: Python application
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

ci/python-package.yml

@@ -1,3 +1,9 @@
+---
+name: Python package
+description: Create and test a Python package on multiple Python versions.
+categories: [Python]
+iconName: python
+---
 # This workflow will install Python dependencies, run tests and lint with a variety of Python versions
 # For more information see: https://help.github.com/actions/language-and-framework-guides/using-python-with-github-actions
 
@@ -5,9 +11,9 @@ name: Python package
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   build:

ci/python-publish.yml

@@ -1,3 +1,9 @@
+---
+name: Publish Python Package
+description: Publish a Python Package to PyPI on release.
+categories: [Python]
+iconName: python
+---
 # This workflows will upload a Python Package using Twine when a release is created
 # For more information see: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries
 

ci/ruby.yml

@@ -1,3 +1,9 @@
+---
+name: Ruby
+description: Build and test a Ruby project with Rake.
+categories: [Ruby]
+iconName: ruby
+---
 # 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
@@ -9,9 +15,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
   test:

ci/rust.yml

@@ -1,13 +1,16 @@
+---
+name: Rust
+description: Build and test a Rust project with Cargo.
+categories: [Rust]
+iconName: rust
+---
 name: Rust
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
-
-env:
-  CARGO_TERM_COLOR: always
+    branches: [ master ]
 
 jobs:
   build:

ci/scala.yml

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

ci/swift.yml

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

ci/tencent.yml

@@ -1,3 +1,9 @@
+---
+name: Tencent Kubernetes Engine
+description: This workflow will build a docker container, publish and deploy it to Tencent Kubernetes Engine (TKE).
+categories: []
+iconName: tencentcloud
+---
 # This workflow will build a docker container, publish and deploy it to Tencent Kubernetes Engine (TKE).
 #
 # To configure this workflow:

ci/terraform.yml

@@ -1,7 +1,13 @@
+---
+name: Terraform
+description: Set up Terraform CLI in your GitHub Actions workflow.
+categories: []
+iconName: terraform
+---
 # This workflow installs the latest version of Terraform CLI and configures the Terraform CLI configuration file
 # with an API token for Terraform Cloud (app.terraform.io). On pull request events, this workflow will run
 # `terraform init`, `terraform fmt`, and `terraform plan` (speculative plan via Terraform Cloud). On push events
-# to the $default-branch branch, `terraform apply` will be executed.
+# to the master branch, `terraform apply` will be executed.
 #
 # Documentation for `hashicorp/setup-terraform` is located here: https://github.com/hashicorp/setup-terraform
 #
@@ -47,7 +53,7 @@ name: 'Terraform'
 on:
   push:
     branches:
-    - $default-branch
+    - master
   pull_request:
 
 jobs:
@@ -65,7 +71,7 @@ jobs:
     - name: Checkout
       uses: actions/checkout@v2
 
-    # Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token
+    # Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token 
     - name: Setup Terraform
       uses: hashicorp/setup-terraform@v1
       with:
@@ -82,9 +88,9 @@ jobs:
     # Generates an execution plan for Terraform
     - name: Terraform Plan
       run: terraform plan
-
-      # On push to $default-branch, build or change infrastructure according to Terraform configuration files
+    
+      # On push to master, build or change infrastructure according to Terraform configuration files
       # Note: It is recommended to set up a required "strict" status check in your repository for "Terraform Cloud". See the documentation on "strict" required status checks for more information: https://help.github.com/en/github/administering-a-repository/types-of-required-status-checks
     - name: Terraform Apply
-      if: github.ref == 'refs/heads/$default-branch' && github.event_name == 'push'
+      if: github.ref == 'refs/heads/master' && github.event_name == 'push'
       run: terraform apply -auto-approve

ci/wpf-dotnet-core.yml

@@ -1,32 +1,38 @@
+---
+name: WPF .NET Core
+description: Build, test and publish a Wpf application built on .NET Core.
+categories: [C#, Visual Basic, WPF, .NET]
+iconName: dotnetcore
+---
 # 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
+# This workflow will build, test and package a WPF desktop application
 # built on .NET Core.
-# To learn how to migrate your existing application to .NET Core,
+# To learn how to migrate your existing WPF 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.
+# 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
+# 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
+# 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".
@@ -36,13 +42,13 @@
 # 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
+name:  WPF .NET Core
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ master ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ master ]
 
 jobs:
 
@@ -52,7 +58,7 @@ jobs:
       matrix:
         configuration: [Debug, Release]
 
-    runs-on: windows-latest  # For a list of available runner types, refer to
+    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:
@@ -81,8 +87,8 @@ jobs:
     - name: Execute unit tests
       run: dotnet test
 
-    # Restore the application to populate the obj folder with RuntimeIdentifiers
-    - name: Restore the application
+    # Restore the WPF application to populate the obj folder with RuntimeIdentifiers
+    - name: Restore the WPF application
       run: msbuild $env:Solution_Name /t:Restore /p:Configuration=$env:Configuration
       env:
         Configuration: ${{ matrix.configuration }}

script/sync-ghes/index.ts

@@ -11,16 +11,6 @@ interface WorkflowDesc {
   iconType?: "svg" | "octicon";
 }
 
-interface WorkflowProperties {
-  name: string;
-
-  description: string;
-
-  iconName?: string;
-
-  categories: string[] | null;
-}
-
 interface WorkflowsCheckResult {
   compatibleWorkflows: WorkflowDesc[];
   incompatibleWorkflows: WorkflowDesc[];
@@ -43,21 +33,16 @@ async function checkWorkflows(
     for (const e of dir) {
       if (e.isFile()) {
         const workflowFilePath = join(folder, e.name);
+        const enabled = await checkWorkflow(workflowFilePath, enabledActions);
+
         const workflowId = basename(e.name, extname(e.name));
-        const workflowProperties: WorkflowProperties = require(join(
+        const workflowProperties = require(join(
           folder,
           "properties",
           `${workflowId}.properties.json`
         ));
         const iconName: string | undefined = workflowProperties["iconName"];
 
-        const isBlankTemplate = workflowId === "blank";
-        const partnerWorkflow = workflowProperties.categories === null;
-
-        const enabled =
-          (isBlankTemplate || !partnerWorkflow) &&
-          (await checkWorkflow(workflowFilePath, enabledActions));
-
         const workflowDesc: WorkflowDesc = {
           folder,
           id: workflowId,

script/validate-data/index.ts

@@ -22,7 +22,6 @@ const propertiesSchema = {
   properties: {
     name: { type: "string", required: true },
     description: { type: "string", required: true },
-    creator: { type: "string", required: false },
     iconName: { type: "string", required: true },
     categories: {
       anyOf: [